Repository navigation
Release Notes
This public release contains the definition and documentation of
- sim-swap-subscriptions 0.4.0
- sim-swap 2.2.0
The API definition(s) are based on
- Commonalities r4.4 (0.9.0)
- Identity and Consent Management r4.2 (0.5.0)
sim-swap-subscriptions 0.4.0
sim-swap-subscriptions 0.4.0 is an initial public version of this API.
Changes documented below are compared to version 0.3.0.
- API definition with inline documentation:
Breaking changes
GET /subscriptionsreturns a paginatedSubscriptionListobject with the required propertiessubscriptionsandpagination, instead of an array of subscriptions, by @bigludo7 in #272
Added
- Pagination for
GET /subscriptions: optionalpageandperPagequery parameters, andlink,x-total-countandx-total-pagesresponse headers, by @bigludo7 in #272 PRIVATE_KEY_JWTassinkCredential.credentialType, together with the422 PRIVATE_KEY_JWT_NOT_CONFIGUREDerror code, by @bigludo7 in #272- Test scenarios for the
409 ALREADY_EXISTSand429 TOO_MANY_REQUESTSerror responses ofcreateSimSwapSubscription, by @albertoramosmonagas in #321
Changed
- Mandatory
info.descriptionsections added or updated (authorization and authentication, additional error responses, request body strictness),serversAPI root variable described, and API Readiness Checklist updated, by @bigludo7 in #272 - Aligned with the Commonalities r4.3 (0.8.0) event subscription template: security schemes,
PhoneNumber,SubscriptionId,Config, the notification event schemas and the error responses are now referenced fromCAMARA_common.yamlandCAMARA_event_common.yamlinstead of being defined locally, by @bigludo7 in #272 - Adopted the request body strictness rule: requests with JSON bodies containing properties not declared in the specification are rejected with
400 INVALID_ARGUMENT, by @bigludo7 in #272 config.subscriptionMaxEventsisint32with a maximum of 1000000, by @rartych in #280info.descriptionextended to document the pagination ofGET /subscriptions(pageandperPage) and the supported sink credential types (ACCESSTOKENandPRIVATE_KEY_JWT), and to state thattypesis mandatory when creating a subscription, by @albertoramosmonagas in #290- Aligned with Commonalities r4.4 (0.9.0): error responses now reference the centralised
CAMARA_common.yamldefinitions, and mandatoryinfo.descriptionsections are updated, by @albertoramosmonagas in #295 - "SIM swap" capitalisation standardised across all operation summaries, descriptions and tags; subscription operation examples unified to UUID format, by @albertoramosmonagas in #305
- Clarified that
phoneNumberin theswappedevent data (EventSwappedData) is only included for subscriptions created with a two-legged access token, so the subscriber identity is not exposed to API consumers using a three-legged access token, by @albertoramosmonagas in #305
Fixed
externalDocs.urlcorrected to point to the SimSwap repository instead of the CAMARA organisation page, by @hdamker in #282- "SIM swap" casing harmonised in the remaining descriptions; notification examples unified to UUID format for
subscriptionId, by @albertoramosmonagas in #309
Removed
protocolvaluesAMQP,KAFKA,MQTT3,MQTT5andNATS, andsinkCredential.credentialTypevaluesPLAINandREFRESHTOKEN, which were already not allowed by the 0.3.0 descriptions, by @bigludo7 in #272- Error code
QUOTA_EXCEEDED(429), not applicable to this API, removed with the Commonalities r4.4 error catalogue;TOO_MANY_REQUESTSremains, by @albertoramosmonagas in #295
sim-swap 2.2.0
sim-swap 2.2.0 is a minor update of this API.
Changes documented below are compared to version 2.1.0.
- API definition with inline documentation:
Breaking changes
- N/A
Added
- Test scenarios for the
429 TOO_MANY_REQUESTSerror response ofcheckSimSwapandretrieveSimSwapDate, by @albertoramosmonagas in #321
Changed
- Tags
Retrieve SIM Swap DateandCheck SIM Swapdefined;x-correlator,PhoneNumber, the security scheme and the error responses are now referenced fromCAMARA_common.yamlinstead of being defined locally; API Readiness Checklist updated, by @bigludo7 in #272 - Adopted the request body strictness rule: requests with JSON bodies containing properties not declared in the specification are rejected with
400 INVALID_ARGUMENT. Per the CAMARA API Design Guide this is not a breaking change; it is the reason for the minor version increase, by @bigludo7 in #272 - Aligned with Commonalities r4.3 (0.8.0): updated mandatory
info.descriptionsections, addedmaxLengthtophoneNumberandx-correlator(values were already bounded by the existing patterns), added bounds to theErrorInfoproperties, and constrainedmonitoredPeriodtoint32in the range 1-999, by @bigludo7 in #272 latestSimChangeclarified to benullwhen the provider cannot return it for privacy reasons (themonitoredPeriodmechanism applies), by @albertoramosmonagas in #290- Aligned with Commonalities r4.4 (0.9.0): error responses now reference the centralised
CAMARA_common.yamldefinitions, and mandatoryinfo.descriptionsections are updated, by @albertoramosmonagas in #295 latestSimChangedescription updated to explicitly reference RFC 3339 date-time format, by @albertoramosmonagas in #305
Fixed
externalDocs.descriptioncorrected to use the "CAMARA" capitalisation, by @hdamker in #282- "SIM swap" casing harmonised in the
info.description, tag and example descriptions, by @albertoramosmonagas in #309
Removed
- Error codes not applicable to this API, removed with the Commonalities r4.4 error catalogue:
NOT_FOUND(404, replaced byIDENTIFIER_NOT_FOUND),QUOTA_EXCEEDED(429,TOO_MANY_REQUESTSremains), andOUT_OF_RANGE(400) inPOST /retrieve-date(still applicable inPOST /check), by @albertoramosmonagas in #295
Full Changelog: r3.3...r4.3