Skip to main content

Passionfroot API: documentation for partners and creators

How to get an API key and use the Partner API and Creator API.

Written by Hugo Ibiapina

Passionfroot has REST APIs for partners (brands) and creators. You can use them to sync your collaborations, placements, proposals and conversations with your CRM, your reporting tools or your AI agents.
​

Full documentation: docs.passionfroot.me
​

Before you start

  • You need a Passionfroot account and an API key.

  • Your API key decides which API you use. A partner key uses the Partner API. A creator key uses the Creator API.

  • Each key only gives access to the data of the account that created it. If an item belongs to another account, the API returns a 404.

How to create an API key

  1. Go to Settings → API in your Passionfroot workspace.

  2. Create a key and choose an expiration date.

  3. Copy the key right away. You can only see the full key once.

  4. Send it in every request, in the header: Authorization: Bearer YOUR_API_KEY

  5. Follow the Quickstart to make your first request.

Important: keep your API key on a server. Never put it in browser code, a mobile app, source control or a support message. Give each integration its own key. If a key leaks, revoke it in Settings → API. Revoking takes a few minutes, so treat the key as active until then.
​

Guides for every integration

  • Authentication: how to create, store and send API keys safely.

  • Pagination: how to go through long lists without missing records.

  • Rate limits: the request limits per key and per IP.

  • Idempotency: how to retry some actions without creating duplicates.

For partners (brands): Partner API

Placements and collaborations

  • List your scheduled placements, with the creator, channel, collaboration and campaign if you need them.

  • List your collaborations, or get one collaboration, with campaign details.

Creators

  • List the creators you have collaborated with, or get one creator, including your private notes and labels.

  • List all labels in your workspace.

Conversations

  • List your conversations, ordered by the latest activity.

  • Read the messages of a conversation. Reading does not mark it as read.

  • Mark a conversation as read.

  • Send a message. It is sent as the team member who created the API key.

  • Send an inquiry to a new creator. This creates the conversation if needed.

Proposals

  • Accept a creator's proposal.

  • Reject a creator's proposal. This also cancels the collaboration.

Partner API reference: docs.passionfroot.me/partners
​

For creators: Creator API (alpha)

The Creator API is in alpha. To use it, first send the one-time access request in Settings → API. Once your access is approved, you can create a key.

Placements and collaborations

  • List your scheduled deliverables.

  • List your collaborations, or get one collaboration.

Partners

  • List the brands you have collaborated with, or get one brand.

Catalog

  • List the products and packages that are visible on your storefront.

Conversations

  • List your conversations, ordered by the latest activity.

  • Read the messages of a conversation. If a conversation is blocked, unblock it in your Inbox first.

  • Send a message to a brand.

  • Mark a conversation as read.

Requests and proposals

  • Accept a brand's package request as it is, or decline it with a reason.

  • Create a proposal with your own products, dates and price.

  • Counter a proposal. This replaces your pending proposal with a new one.

  • Accept a brand's proposal, or reject it. Rejecting cancels the collaboration and frees the dates.

About prices: the prices you read in the Creator API are your earnings after Passionfroot fees and before taxes, not the amount the brand paid. When you create a proposal, the price you send is your list price, in the currency of the collaboration.

Creator API reference: docs.passionfroot.me/creators
​

Using the API with AI tools

Passionfroot does not have an MCP server. To use the API with an AI agent, give the agent one of these files, so it can learn the API before it writes an integration:

Developers can also use the OpenAPI specs: Partner API and Creator API.
​

Common errors

  • 401: the key is missing, invalid, revoked or expired. Check the key, and replace it if needed.

  • 403: your account does not have permission for this action. Check that your account has API access.

  • 404: the item does not exist, or it belongs to another account.

  • 503: the key check is not available for a moment. Try again later, and do not replace a valid key.

If you need help, contact us through the chat in your workspace. Please never share your API key with us.

Did this answer your question?