<aside> ℹ️ As a platform, Captain Data values its SaaS Partners a lot.

The following lists all Partners integrated inside the Captain Data's platform.

</aside>

Saas Partners

💫 Feature your product

📘 Documentation

<aside> ℹ️

Want to integrate your solution with Captain Data? Here’s our complete documentation to provide us with a detailed JSON file that we’ll implement for you 🙂

</aside>

1. Request Section

1.1 Authentication (auth)

The auth section is used to specify the authentication method required for the integration. We support different types of authentication, including API keys and OAuth tokens.

Fields:

• type: The type of authentication. Options include:
  • apiKey: Use when the integration requires an API key.
  • OAuth: Use for OAuth-based integrations.
• key: The field where the key or token is passed (e.g., Authorization for bearer tokens or api_key).
• position: Where the authentication key is placed. Possible values:
  • header: The key is passed in the headers.
  • uri: The key is included in the URL.
• prefix (Optional): A prefix that can be added before the key (e.g., Bearer for OAuth tokens).

Examples:

API Key in the Header:

"auth": {
  "type": "apiKey",
  "key": "Authorization",
  "position": "header",
  "prefix": "Bearer "
}

API Key in the URI:

"auth": {
  "type": "apiKey",
  "key": "api_key",
  "position": "uri"
}