How to apply for Juno partner access, how the key is delivered, and how to call the Juno Partner API.

• Apply here: https://www.usejuno.io/partners

• Who this is for: partners who want to list jobs and read job data through the Juno Partner API.

• Turnaround: applications are reviewed manually. You receive an email at the address on the application once a decision is made.

> Key delivery: we never email the API key itself. On approval we email a single-use claim link that is valid for 24 hours. The key is only shown once, on that page.

1. Before you apply

Have the following ready. The application form asks for exactly these fields.

> The claim link is always sent to contactEmail. Use a shared/team inbox if the person who applies may change.

2. Making the request

• Go to

  https://www.usejuno.io/partners

  .

• Fill in every required field from the table above. Be specific in audienceDescription — vague applications take longer to review.

• Submit the form. The submission is stored as a pending application and a request is raised for review.

• Wait for the review email. Do not resubmit the same application; duplicate pending applications for the same contactEmail are ignored.

Application statuses you may see:

• pending

  — submitted, awaiting review.

• approved

  — reviewed and cleared; a key can be issued and claimed.

• rejected

  — not accepted, with a reason.

• revoked

  — previously approved access has been withdrawn.

3. The emails that get sent

3a. Approval email — claim link only (sent on approval)

The email does not contain the key. It contains a single-use link to claim it. The link is valid for 24 hours.

3b. Claim page (what the link opens)

A tiny page that:

• Shows the API key once, with a copy button.

• Warns that the key will not be shown again.

• Invalidates the link as soon as it is opened (or when the 24 hours elapse).

3c. Rejection / revocation email

Sent when an application is not approved or access is withdrawn. It states the

reason. A revoked partner must stop using the key immediately; the old key is

deactivated server-side.

4. How to call the API

Once the partner has claimed the key, every request is authenticated with it.

Base URL

https://api.usejuno.io/v1/developer

Authentication — send the key on every request, either header works:

X-API-Key: jdp_live_<...>

or

Authorization: Bearer jdp_live_<...>

Keys are prefixed with jdp_live_ so they are easy to identify in logs and

secret scanners.

Sample request — list job rankings

curl -X GET "https://api.usejuno.io/v1/developer/rankings" \ -H "X-API-Key: $JUNO_PARTNER_API_KEY"

Sample request — view a single ranking

curl -X GET "https://api.usejuno.io/v1/developer/rankings/<rankingId>" \ -H "X-API-Key: $JUNO_PARTNER_API_KEY"

Common status codes

Notes

• The JDP partner key is scoped to

  read:jobs

  .

• Requests are rate limited per key. Repeated failures or abuse can disable a key.

• Key lifecycle events (issued, claimed, disabled, enabled, revoked) are recorded

on the application as activity history.

5. After approval

• The key is bound to your approved application and scoped to the Partner API.

• Store the key in a secret manager — never in source control, chat, or a ticket.

• If the key is ever exposed or lost, do not ask us to resend the link. Request a

Request for revoke and reissue; a brand-new key and a brand-new claim link are generated.

Why

• The raw key never sits in an inbox, so it can't leak from email history,

forwards, or backups.

• The database only ever stores a hash, so a database read cannot recover the key.

• A short-lived, single-use link limits the window and the number of times the

secret can be viewed.

Reference

• Apply:

  https://www.usejuno.io/partners

• API base:

  https://api.usejuno.io/v1/developer

• Auth header:

  X-API-Key: jdp_live_<...>

  or

  Authorization: Bearer jdp_live_<...>

• Scope:

  read:jobs

• Claim link:

  https://app.usejuno.io/partner/key/<token>

  (single-use, 24 hours)

• Support: support@usejuno.io