Skip to main content

Cookies on Furmissions

We use some essential cookies to make Furmissions work. We’d also like to use additional cookies to understand how you use the site and improve it. We don’t set these unless you accept them.

View cookies

Hi! Sign in or register

Furmissions

Payments Payments via stripe is currently unavailable. Please use other alternative methods.

BETA Site has been released under Beta phrase. Bugs may occur. Any issues you can let us know. Report a bug

API reference

Read your Furmissions data from your own tools with an API key.

Getting a key

  • Member keys: Settings → API keys. A member key acts as you, and only sees what you could see on the site.
  • Server keys: made by staff in Staff → System → API keys, for the site’s own systems.
  • Each key has its own permissions, rate limit and expiry, and can be revoked at any time. Keys are shown once: keep them secret and never put them in a public website or app.

Sending requests

Base address: https://furmissions.com/api/v1. Send the key in the Authorization header. Responses are JSON; lists are paginated with data, links and meta.

curl https://furmissions.com/api/v1/me \
  -H "Authorization: Bearer fmk_xxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Accept: application/json"
StatusMeaning
401No key, wrong key, or the key was revoked, expired or used from a blocked IP address.
403The key is missing a permission, or is the wrong kind (member or server) for this address.
404Not found, or not yours.
422A filter or field isn’t valid; the response says which.
429Too many requests. Wait for the Retry-After seconds. X-RateLimit-Limit and X-RateLimit-Remaining show where you are.

Member endpoints

RequestPermissionWhat it returns
GET /meprofile:readYour profile, Premium status and upload allowance.
GET /ordersorders:readYour purchases and your stores’ orders. Filters: role=buyer|seller, status, per_page (max 100).
GET /orders/{uuid}orders:readOne order you’re part of.
GET /listingslistings:readListings in stores you manage. Filters: status, per_page.
PATCH /listings/{id}listings:writePause or resume (status: active|paused) or set stock (number or null).
GET /conversationsmessages:readYour buyer and seller chats, newest first.
GET /notificationsnotifications:readYour notifications.
GET /creditscredits:readCredit balances and the last 50 changes.
All permissions
  • profile:read: See your profile, Premium status and upload allowance
  • orders:read: See your purchases and your stores’ orders
  • messages:read: See your buyer and seller conversations
  • notifications:read: See your notifications
  • credits:read: See your credit balances and history
  • listings:read: See your stores’ listings (sellers)
  • listings:write: Pause, resume and change stock on your stores’ listings (sellers)

Server endpoints

RequestPermissionWhat it returns
GET /server/healthhealth:readCron, queue and disk health. Returns 200 when healthy and 503 when not, so uptime monitors can watch it.
GET /server/statsstats:readSales and growth figures for the last 30 days.
GET /server/accountsaccounts:readMember accounts. Filters: q (name, email or username), per_page.
GET /server/accounts/{id}accounts:readOne account with its stores and credit.
GET /server/ordersorders:read-allEvery order. Filters: status, since (date), per_page.
GET /server/listingslistings:read-allEvery listing. Filters: status, per_page.
GET /server/ticketstickets:readSupport tickets and disputes. Filters: category, status, per_page.
All permissions
  • health:read: Check cron, queue and disk health (for uptime monitors)
  • stats:read: Read sales and growth figures
  • accounts:read: Read member accounts (never passwords or secrets)
  • orders:read-all: Read every order
  • listings:read-all: Read every listing
  • tickets:read: Read support tickets and disputes