Skip to Content
Prets Developer Portal

Introduction

How the Prets API is organized: base URL, request format, authentication, and the conventions every endpoint shares.

The Prets API is a JSON API over HTTPS. You use it to create and read quotes, follow up on cases, and register the endpoint that receives your events.

Base URL

https://api.prets.app

Every path starts with the major version, for example /v1/quotes. See Versioning.

Requests and responses

  • Send request bodies as JSON with Content-Type: application/json.
  • Responses are JSON. Quotes and cases come back under data. Lists use the same data key plus pagination fields; see Pagination.
  • Ids are prefixed strings, such as qot_… for quotes, cas_… for cases, and evt_… for events. Treat them as opaque.
  • Timestamps are ISO 8601 strings in UTC, for example 2026-06-01T12:00:00.000Z.
  • Amounts are numbers in euros, not cents: 25000 is €25,000. See Quote amounts.

Your first request

Create an API key in the partner portal, then list your quotes:

curl https://api.prets.app/v1/quotes?limit=2 \
  -H "Authorization: Bearer ak_..."
{
  "data": [
    { "quoteId": "qot_01ARZ3NDEKTSV4RRFFQ69G5AV", "...": "..." }
  ],
  "hasMore": true,
  "links": {
    "next": {
      "href": "/v1/quotes?cursor=eyJ...",
      "cursor": "eyJ..."
    }
  }
}

Resources

ResourceWhat it is
QuotesAn installer's offer to a consumer, and the financing journey attached to it.
CasesA support conversation about a quote, between you and Prets.
Event destinationsThe HTTPS endpoint where Prets sends your events.

Events, such as quote.created or case.closed, are listed under the Events tab.

Live and sandbox organizations

There is no separate test mode and no test key prefix. Every request acts on the organization that owns the API key. Whether an organization is live or a sandbox is set by Prets, not by the key.

Conventions

On this page