Flare

Flare API API

Using our easy-to-use REST API you can administer projects, errors, and performance monitoring data.

GitHub OpenAPI

Operations 27

GET /projects/match Find a Flare project for a Laravel Cloud application. #
GET /me Get the authenticated user. #
GET /projects Get all projects. #
POST /projects Create a new project. #
PATCH /projects/{project_id} Update a project. #
DELETE /projects/{project_id} Delete a project. #
GET /projects/{project_id}/errors Get all errors within a project. #
GET /projects/{project_id}/error-count Get the number of errors in the given period. #
GET /projects/{project_id}/error-occurrence-count Get the number of error occurrences in the given period. #
GET /teams/{team_id} Get a team. #
DELETE /teams/{team_id}/users/{user_id} Remove a user from a team. #
GET /errors/{error_id}/occurrences Get all occurrences for an error. #
GET /errors/{error_id}/insights/{insight_type} Get paginated insights for an error. #
POST /errors/{error_id}/resolve Resolve an error. #
POST /errors/{error_id}/open Reopen an error. #
POST /errors/{error_id}/snooze Snooze an error. #
POST /errors/{error_id}/unsnooze Unsnooze an error. #
POST /errors/{error_id}/notes Add a note to an error. #
GET /error-occurrences/{occurrence_id} Get an error occurrence. #
GET /error-occurrences/{occurrence_id}/previous-exceptions/{previous_exception_id} Get the frames of a previous exception in an occurrence's exception chain. #
GET /projects/{project_id}/monitoring/summary Get the monitoring dashboard summary. #
GET /projects/{project_id}/monitoring/{type} List aggregations by type. #
GET /projects/{project_id}/monitoring/{type}/time-series Get time series data for an aggregation type. #
GET /aggregations/{type}/{uuid} Get a single aggregation with detail. #
GET /aggregations/{type}/{uuid}/traces List traces for an aggregation. #
GET /traces/{traceId} Get the full span tree for a trace. #
GET /projects/{project_id}/logs List log entries with cursor pagination. #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/flareapp-io/openapi/_original/flareapp-io-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/flareapp-io/json-schema/flareapp-io-monitoring-trend-schema.json
📊
JSONSchema
https://artifacts.apis.io/flareapp-io/json-schema/flareapp-io-base-project-schema.json
📊
JSONSchema
https://artifacts.apis.io/flareapp-io/json-schema/flareapp-io-paginated-result-schema.json
📊
JSONSchema
https://artifacts.apis.io/flareapp-io/json-schema/flareapp-io-monitoring-aggregation-schema.json
📊
JSONSchema
https://artifacts.apis.io/flareapp-io/json-schema/flareapp-io-error-occurrence-schema.json
📊
JSONSchema
https://artifacts.apis.io/flareapp-io/json-schema/flareapp-io-monitoring-metrics-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/flareapp-io:flare-api-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

flareapp-io-api-openapi.yml Raw ↑ 
openapi: 3.1.0
info:
  title: Flare API
  description: >-
    Using our easy-to-use REST API you can administer projects, errors, and
    performance monitoring data.


    ## Authentication


    Authenticate with a personal access token. Every request should include
    an `Accept: application/json` header.


    ### Personal access tokens


    Create one under [Account → API access](/account/api-access),
    scoped to the teams and projects you choose and to one or more of the
    `read`, `write`, and `admin` scopes. Send it as a Bearer header.


    ```shellscript

    curl "https://flareapp.io/api/projects" \

    -H 'Authorization: Bearer <token>' \

    -H 'Accept: application/json'

    ```


    ### Legacy API tokens


    Legacy API tokens predate personal access tokens. They grant full access
    to every team and project the issuing user belongs to and cannot be
    scoped further. New integrations should use a personal access token
    instead. Legacy tokens accept either a Bearer header or an `api_token`
    query parameter.


    ```shellscript

    curl "https://flareapp.io/api/projects?api_token=<token>" \

    -H 'Accept: application/json'

    ```


    ## Scopes


    Personal access tokens carry one or more scopes that control which
    endpoints they can call. Requests made with a token that is missing the
    required scope return `403`.


    | Scope   | What it grants                                                            |

    | ------- | ------------------------------------------------------------------------- |

    | `read`  | Read errors, logs, traces, projects, and team data.                       |

    | `write` | Resolve, snooze, comment, upload sourcemaps, change settings.             |

    | `admin` | Manage team membership, billing, projects, and API keys.                  |


    Each operation in this reference declares the scope it requires under
    its security section. Legacy API tokens bypass scope checks.


    ## Pagination


    Most paginated endpoints follow the JSON:API pagination specification.


    #### Query Parameters

    - `page[number]` - The page number (default: 1, minimum: 1)

    - `page[size]` - Number of items per page (default: 10, minimum: 1, maximum:
    30)


    #### Response Structure

    All paginated responses include:

    - `data` - Array of items for the current page

    - `meta` - Pagination metadata including current_page, total, per_page, from,
    to, last_page

    - `links` - Navigation links for first, last, previous, and next pages


    #### Example

    ```shellscript

    curl "https://flareapp.io/api/projects?page[number]=2&page[size]=15" \

    -H 'Authorization: Bearer xyz123' \

    -H 'Accept: application/json'

    ```


    #### Cursor Pagination (Logs)


    The logs endpoint uses cursor-based pagination instead of page numbers.
    Use `cursor[timestamp]` and `cursor[uuid]` from a previous response
    together with `cursor[direction]=before` (older than the cursor) or
    `cursor[direction]=after` (newer than the cursor) to fetch additional
    pages. The `order` parameter (`asc` or `desc`, default `desc`)
    controls the order of rows in the response and is independent of the
    cursor direction. Use `page[size]` to control the number of items per
    page (default: 100, max: 1000). The `meta.has_more` field indicates
    whether more results are available.
  version: 1.0.0
  contact:
    name: Flare
    url: https://flareapp.io
    email: support@flareapp.io
  x-logo:
    url: "https://flareapp.io/android-chrome-512x512.png"
    backgroundColor: "rgb(250, 250, 250)"
    altText: "Flare logo"
servers:
  - url: https://flareapp.io/api
security:
  - OAuth2: [read]
  - BearerAuth: []


# --- truncated at 32 KB (135 KB total) ---
# Full source: https://artifacts.apis.io/flareapp-io/openapi/_original/flareapp-io-api-openapi.yml