Using the Oshop247 API for integrations

Integrations extend your store — accounting exports, marketing pixels, custom fulfilment tools. This article explains what Oshop247 merchants can connect today without custom code, and how higher plans access deeper integration support.

Payment gateway integrations (built-in)

These are the most critical integrations for Nigerian and international stores:

• Paystack — Settings → Payments; supports cards, transfer, USSD
• Flutterwave — same Payments tab; strong for multi-country Africa
• Stripe — for UK, US, Canada and other Stripe-enabled markets

Each gateway uses API keys you paste into admin. For Stripe, also configure webhook secret so payment events update order status reliably.

Webhook setup (Stripe example)

1. In Stripe Dashboard, create a webhook endpoint pointing to your store's Stripe webhook URL (shown in Oshop247 payment settings or docs)
2. Select events such as checkout.session.completed and invoice.paid
3. Copy the signing secret into Settings → Payments → Stripe webhook secret
4. Run a test payment to confirm orders mark paid automatically

Marketing and analytics

Under Settings → SEO, add:

• Google Analytics ID — track storefront traffic and conversions
• Facebook Pixel ID — measure ad performance and build retargeting audiences

These scripts load on your customer-facing storefront, not in admin.

Email delivery integrations

Settings → Email / SMTP supports providers like SMTP, Mailgun, Amazon SES, and Resend. Custom SMTP sends order confirmations from your domain (@yourbrand.com) instead of a generic sender — improves deliverability and trust.

Data export for accounting

Use Reports exports and order CSV downloads to feed accounting tools (Excel, QuickBooks workflows, local Nigerian accountants). Scheduled advanced reports on Business plans reduce manual export work.

Custom domain

Connect your branded domain so customers see your URL at checkout — important for ads and email campaigns. DNS setup is guided in admin domain settings.

Custom integrations and API access

Enterprise and custom-integration plans may include REST API access, higher rate limits, and webhook subscriptions for orders and inventory. If you need:

• Real-time sync with external ERP
• Custom mobile app tied to your catalog
• Marketplace middleware

Contact Oshop247 support or sales with your use case. Standard store admin does not expose a public API key panel unless your plan includes custom_integrations.

Security principles

• Never paste secret keys in client-side JavaScript or public GitHub repos
• Rotate keys when staff with access leaves
• Verify webhook signatures before trusting external payloads

Start with built-in integrations — payments, analytics, SMTP — before building custom API middleware. They cover 90% of merchant needs.