Skip to main content

Download JSON

Use this file to connect Jobin inside tools like Claude, n8n, Make, Postman, or a generated client.

API Reference

Human-readable workflow and endpoint guidance for the same public API surface.

Try It: Validate API Key

Test your API key before building automations.

Try It: Assign Contacts To Campaign

Example: automatically add leads into a Jobin sequence.

​
What This File Is

This JSON file is the machine-readable source of truth for the public Jobin API. Use it when a tool needs exact endpoint paths, request bodies, authentication requirements, or response schemas.

​
Best Way To Use This With AI Agents

Agents perform best when they receive:
  1. /openapi/jobin-integration.json for the exact API contract
  2. /api-reference/introduction for Jobin-specific workflow rules and rate limits
  3. /quickstart when the goal is “get the first working flow running”
This combination matters because the schema defines the interface, but companion docs explain the business rule that Jobin UI sequences map to API campaigns.

​
How You Will Actually Use This

​
In n8n / Make

  • Import the JSON into an HTTP / OpenAPI module
  • Get pre-filled endpoints and schemas
  • Build flows like: "new lead" -> "assign contact to Jobin campaign"

​
In Zapier

  • Use Webhooks or custom API request steps
  • Copy endpoints from the interactive reference when you need field-level examples
  • Map fields visually without writing a custom backend

​
In Claude / ChatGPT / coding agents

  • Import or paste the spec into the tool
  • Give the agent /api-reference/introduction or /quickstart at the same time
  • Ask for concrete outcomes such as "validate this API key", "find a contact by email", or "assign this contact to a campaign"

​
What This Spec Powers

  • Typed API clients
  • AI-agent workflows
  • Visual automation builders such as n8n and Make
  • Postman or Insomnia imports
  • Consistent request and response handling across tools

​
Base URL

​
Mental Model

Think about the core workflow like this:
  • Trigger -> something happens in your system
  • Action -> call the Jobin API
  • Result -> the contact is enriched or added to a campaign
For most integrations, the first reliable path is:
  1. Validate the API key
  2. Find or import the contact
  3. Optionally enrich the contact
  4. Assign the contact to a campaign