Floyo API - Introduction
7 min
you can use the floyo api to programmatically run workflows and manage your assets without having to use comfyui interface the floyo api is organized around rest it has predictable resource oriented urls, accepts form encoded request bodies, returns json encoded responses, and uses standard http response codes, authentication, and verbs base url all api requests are served over https to ensure data encryption and security unencrypted http requests will be rejected the base url for all api endpoints is https //api floyo ai authentication the floyo api uses api keys to authenticate requests you can manage your api keys in your team's settings > floyo api protect your credentials your api keys carry significant privileges to prevent unauthorized access, never share your secret keys in publicly accessible areas such as github, client side code, or mobile applications the bearer token all api requests must be made over https to authenticate, you must include a bearer token in the authorization header of every request example header authorization bearer your api key rate limits we limit the number of rest api requests that you can make within a specific amount of time this limit helps prevent abuse and denial of service attacks and ensures that the api remains available for all users requests are rate limited to 100 requests per minute, per api key if you exceed this limit, the api will return a 429 too many requests response wait for the next minute window to resume making requests errors floyo api uses conventional http response codes to indicate the success or failure of an api request codes in the 2xx range indicate success codes in the 4xx range indicate an error that failed given the information provided (e g , a required parameter was omitted, api key was missing or invalid, etc ) codes in the 5xx range indicate an error with floyo's servers (these are rare) failed responses include an `error` and `message` attributes error is the short error message, i e 'run not found' message is an optional error message including an explanation of the error
