Pred Authentication API
Required headers, token refresh, and EIP-712 CreateProxy signature for login. For overview, getting started, and environment configuration, see **Overview**.## Required headers- `Authorization: Bearer ` (for authenticated endpoints)- `X-API-Key: ` (required for login-with-signature only)- `X-Wallet-Address: ` (for order and portfolio endpoints)- `X-Proxy-Address: ` (for order and portfolio endpoints)**Token refresh:** Access tokens are automatically refreshed by the SDK whenever their remaining lifetime drops below the configured threshold. The default threshold is **5 minutes**, and can be overridden via the `RefreshThresholdSeconds` client option.## EIP-712 login signature — CreateProxyFormat: `0x` (132 hex characters). Low-s normalized: `s verifyingContract: ```**Message:**```CreateProxy type: "CreateProxy(address paymentToken,uint256 payment,address paymentReceiver)"paymentToken: 0x0000000000000000000000000000000000000000payment: 0paymentReceiver: 0x0000000000000000000000000000000000000000```**Normalization constants:**- `curveOrder = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141`- `curveOrderHalf = 0x7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF5D576E7357A4501DDFE92F46681B20A0`
Pred Authentication API is one of 7 APIs that Pred publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.
This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against 2 base URLs: https://testnet.pred.app, https://www.pred.app.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Pred Authentication API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
BearerAuth— JWT access token from login endpoint
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.
Required headers, token refresh, and EIP-712 CreateProxy signature for login. For overview, getting started, and environment configuration, see Overview. Required headers - Author…
Schemas 5
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are LoginResponse (3 properties), Error (3 properties), ErrorResponse (3 properties), RefreshTokenResponse (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Pred 6
Other APIs Pred publishes across the network.
This is an independent, third-party profile of Pred Authentication API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.