Skip to main content

​
Credentials

  • Create API keys in Jobin integrations under Custom integration.
  • Send the API key in x-api-key.
  • New public integrations should not depend on the browser token or refresh-token flow.
  • Use https://my.jobin.cloud/api/openapi/v1/auth/validate to verify the API key before launching automation flows.

​
Rate Limits

Because Jobin operations are downstream-provider sensitive, clients should follow conservative limits:
  • keep read traffic modest and burst-free
  • treat enrichment and DM endpoints as side-effecting operations
  • avoid firing multiple concurrent DM jobs for the same sender and contact
  • use exponential backoff on 429, 408, and 5xx
  • make retries idempotent on the client side whenever possible
  1. Search or fetch the target contact.
  2. Trigger enrichment only when required fields are missing.
  3. Poll the enrichment report until it is terminal.
  4. Assign the contact to a sequence to launch the configured email, SMS, message or invite flow.

​
Error Handling

Expect these categories:
  • 400 for malformed ids or invalid request bodies
  • 401 for invalid API keys
  • 403 for legacy bearer tokens that do not contain the required auth claims
  • 404 when a contact, campaign, or report is outside the authenticated workgroup scope
  • 202 when work has been accepted but will complete asynchronously