Expand description
Shared JSON:API envelope types used across every App Metadata resource.
Resource-specific attribute structs live in their own modules
(app, app_store_version, …) and plug into these generics.
Structs§
- ApiError
- Create
Body - Create
Data - Document
- A single-resource JSON:API document — the body of e.g.
GET /v1/apps/{id}or the response to aPOST/PATCH. - Error
Document - The
errorsenvelope App Store Connect returns on non-2xx responses. - Links
- The JSON:API pagination links on a collection response.
- List
Document - A resource-collection JSON:API document — the body of e.g.
GET /v1/apps. - Optional
Document - A single-resource document whose
datamay benull, as Apple returns for a to-one related resource that isn’t set, e.g.GET /v1/appStoreVersions/{id}/buildon a version with no build attached. - Resource
- A single JSON:API resource object: its id, type, and typed attributes.
Relationships are intentionally left untyped (
serde_json::Value) — this crate builds relationship payloads explicitly on requests rather than typing every relationship shape App Store Connect can return. - Resource
Id - A bare
{ type, id }resource identifier, used to point a create request’s relationships at an existing resource. - ToMany
- A to-many relationship payload, e.g.
relationships.certificateson aPOST /v1/profilesbody. - ToOne
- A to-one relationship payload, e.g.
relationships.appon aPOST /v1/appStoreVersionsbody. - Update
Body - Update
Data - Update
Relationships Body - A
PATCHbody that updates only relationships (no attributes) — e.g. attaching aBuildto anAppStoreVersion. - Update
Relationships Data
Functions§
- path_
and_ query - Turn an absolute
Links::nextURL into the path-and-query formClient::requestwants, since that method prefixes its own base URL and cannot be handed a whole URL.