Creates a Dynamic Content API client instance. You must provide credentials that will be used to authenticate with the API.
OptionaldcConfig: DynamicContentConfigOptional configuration settings for Dynamic Content
OptionalhttpClient: AxiosRequestConfig<any> | HttpClientOptional request settings, can be used to provide proxy settings, add interceptors etc
ReadonlycontentContent Item Resources
Retrieve a content item resource by id
ReadonlycontentContent Repository Resources
Retrieve a content repository resource by id
ReadonlycontentContent Type Resources
Retrieve a content type resource by id
ReadonlycontentGets a content type schemas
Gets a content type schemas
ReadonlyeditionsEdition Resources
Retrieve an edition resource by id
ReadonlyeventsEvent Resources
Retrieve an event resource by id
ReadonlyextensionsExtension Resources
Retrieve an extension resource by id
ReadonlyfoldersRetrieve a folder resource by id
ReadonlyhierarchiesHierarchy Resources
ReadonlyhubsHub Resources
ReadonlypublishingPublishing Job
Get publishing job by id *
ReadonlysnapshotsSnapshot Resources
Retrieve a snapshot resource by id
ReadonlyworkflowWorkflow States
Retrieve a Workflow State by id
Amplience Dynamic Content API client.
Your application should avoid where possible creating a new client for each request. Authentication tokens are cached by the client and only re-requested when they expire, allowing performance to be improved by reusing the client across requests.
If multiple sets of credentials are required your application should create one client per credential set.
Example: