Account

Create a saved config profile

Creates a saved config profile for the signed-in consumer. Names are case-insensitively unique per consumer (a collision returns 409 PROFILE_NAME_TAKEN). A soft per-consumer cap applies (409 PROFILE_LIMIT_REACHED) — it is a UX guard, not a security invariant, so it is enforced application-side rather than via an advisory-lock RPC (contrast the api_keys max-3 limit). The config bundle is byte-bounded; an oversized bundle returns 400. Session-cookie auth (NOT Bearer). No audit_log row is written — saved profiles are low-value config and provenance_log already records every response on this surface. Naturally idempotent: a retried create returns a deterministic 409 PROFILE_NAME_TAKEN via the unique-name constraint, never a duplicate row. The withIdempotency middleware is Bearer-key-coupled (authenticateRequestCached) and does not apply to this session-cookie surface — same posture as the sibling key endpoints.

post/api/v1/account/profiles

Request

Base URL: https://www.apier.no
URL: https://www.apier.no/api/v1/account/profiles
Auth: API key in cookie sb-access-token

Request body

namestring required

Human-readable label shown in the dashboard profile list. Case-insensitively unique per consumer.

Response

Profile created.

successtrue required

Example response

{
  "_meta": {
    "rulebook_version": "v1.0.0",
    "source": "apier.no",
    "data_source": "Brønnøysund Enhetsregisteret + Apier Universal Rulebook",
    "schema_version": "1.0.0",
    "legal_basis": "NLOD — public registry reuse",
    "response_timestamp": "2026-04-24T12:00:00.000Z",
    "response_hash": "sha256:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
    "source_snapshot_id": "brreg-2026-04-24T02:00:00.000Z",
    "cost_nok": 0.5,
    "wallet_remaining_nok": 9.5,
    "spend_cap_remaining_nok": 12.5
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.