Amazon AppSync · Schema
UpdateSourceApiAssociationRequest
Amazon AppSyncGraphQLAPI ManagementServerlessAmazon Web Services
Properties
| Name | Type | Description |
|---|---|---|
| associationId | string | The ID generated by the AppSync service for the source API association. |
| mergedApiIdentifier | string | The identifier of the AppSync Merged API. This is generated by the AppSync service. In most cases, Merged APIs (especially in your account) only require the API ID value or ARN of the merged API. Howe |
| description | string | The description field. |
| sourceApiAssociationConfig | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/amazon-appsync/json-schema/amazon-appsync-update-source-api-association-request-schema.json",
"title": "UpdateSourceApiAssociationRequest",
"x-generated": "2026-11-11",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/amazon-appsync-sourceapiassociations-api-openapi.yml#/components/schemas/UpdateSourceApiAssociationRequest",
"type": "object",
"properties": {
"associationId": {
"type": "string",
"description": "The ID generated by the AppSync service for the source API association."
},
"mergedApiIdentifier": {
"type": "string",
"description": "The identifier of the AppSync Merged API. This is generated by the AppSync service. In most cases, Merged APIs (especially in your account) only require the API ID value or ARN of the merged API. However, Merged APIs in other accounts (cross-account use cases) strictly require the full resource ARN of the merged API."
},
"description": {
"type": "string",
"description": "The description field."
},
"sourceApiAssociationConfig": {
"$ref": "#/$defs/SourceApiAssociationConfig"
}
},
"required": [
"associationId",
"mergedApiIdentifier"
],
"$defs": {
"SourceApiAssociationConfig": {
"type": "object",
"properties": {
"mergeType": {
"type": "string",
"enum": [
"MANUAL_MERGE",
"AUTO_MERGE"
],
"description": "The property that indicates which merging option is enabled in the source API association. Valid merge types are MANUAL_MERGE (default) and AUTO_MERGE. Manual merges are the default behavior and require the user to trigger any changes from the source APIs to the merged API manually. Auto merges subscribe the merged API to the changes performed on the source APIs so that any change in the source APIs are also made to the merged API. Auto merges use MergedApiExecutionRoleArn to perform merge operations."
}
}
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/amazon-appsync-update-source-api-association-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.