Skip to main content

API-Based Integration

API integration allows you to push products and advertisers directly to GoWit via HTTPS requests, achieving near real-time synchronization. In this approach, your system will call GoWit’s Catalog API endpoints to create or update records. This section covers the API endpoints for product and advertiser ingestion, required payload structure, headers/authentication, and examples of using the API.

Authentication & Endpoint Base URL​

To use the API, you must have GoWit API credentials (an API key or token associated with your account). All requests must include this credential in an Authorization header. Typically, GoWit provides a token or key string — e.g., an API secret — to use. Include it like:

Authorization: <YOUR_API_KEY>

Make sure to keep this key secure, as it grants access to your account’s data.

The API base URL will be something like:

https://<your-environment>.gowit.com/api

You will be informed of the exact base URL (which may differ for dev, staging, prod environments).

Data Source UUID​

In addition to the API key, partners may also be asked to include a Data Source UUID in request headers. This UUID is issued when a data source is created in GoWit (e.g., during catalog integration). It is critical for:

  • Monitoring & Observability – lets you trace each request in GoWit’s dashboards.

  • Debugging – helps identify failed syncs or mismatched payloads.

  • Validation – ensures your requests are correctly attributed to the right data source.

Example header:

Data-Source-UUID: 12dc2e2f-fb98-4b77-93ea-d452e19xxxx

Troubleshooting & Debugging Tips​

  • Always verify that both Authorization and Data-Source-UUID headers are present in integration calls.

  • If requests aren’t visible in logs, check that the correct UUID is being used.

  • For staging, make sure you’re using the staging-specific key and UUID, not production values.

For further information please refer to Synchronization & Troubleshooting