What authentication does the JuJu API use?

The JuJu API authenticates with Bearer keys per its OpenAPI spec: a publisher API key is required on the job and feed endpoints, and a separate per-sponsor callback key is used on the conversion postback. Keys are presented in the Authorization header, and the X-API-Key header is not accepted. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I search job postings with the JuJu API?

Yes. The job search endpoint returns active postings with filters, a single-job endpoint retrieves one by its compound id, and a count endpoint reports the total indexed jobs. Application clicks are redirected and attributed through tracked links.

Is there a JuJu MCP server?

You don't need an MCP server to give your agent the JuJu API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the job search and feed endpoints it needs.

Can I limit what my agent is allowed to do with the JuJu API?

Yes. Write a rule that allows only the job search and read operations, so a job-matching agent can query postings while billing, campaign, and account changes stay out of reach, and every call it makes is logged.

What are the rate limits for the JuJu API?

The OpenAPI spec does not publish specific rate limits. JuJu exposes an API-usage report you can read to track your consumption. Check with JuJu for the limits that apply to your publisher or sponsor key.

How do I search jobs with the JuJu API through Jentic?

Search Jentic for an intent like 'search job postings', and it returns the JuJu job search operation with its input schema so your agent calls it with a query. Your stored key is injected at call time, so your agent reaches JuJu without ever handling the credential.