Can HumDay connect to ART19 Content Documentation?

Yes. HumDay reads ART19 Content Documentation's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 22 operations are documented.

Do I need to write code to automate ART19 Content Documentation?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your ART19 Content Documentation account.

What can HumDay do in ART19 Content Documentation?

0 of the 22 documented operations change something in ART19 Content Documentation, and 22 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my ART19 Content Documentation account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to ART19 Content Documentation is held behind that approval.

Automate ART19 Content Documentation

HumDay reads ART19 Content Documentation’s own published API description and derives 22 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What ART19 Content Documentation is

The ART19 Content API conforms to the [JSON:API specification](http://jsonapi.org). API requests **MUST** use the HTTP Accept header: `Accept: application/vnd.api+json` API requests **MUST** be authenticated using the HTTP Authorization header: `Authorization: Token token="your-token", credential="your-credential"` ## General Notes Some query parameters use unencoded [ and ] characters simply for

API host: art19.com

What HumDay can read from ART19 Content Documentation

These are the operations a schedule or a trigger can watch.

GETGet a list of images/images
GETGet a list of people/people
GETGet a list of series/series
GETGet a list of credits/credits
GETGet a list of seasons/seasons
GETGet a list of episodes/episodes
GETGet a list of networks/networks
GETGet a list of media assets/media_assets
GETGet a list of classifications/classifications
GETGet ClassificationInclusion records/classification_inclusions
GETGet a specific image/images/{id}
GETGet a specific person/people/{id}
GETGet a specific series/series/{id}
GETGet a specific credit/credits/{id}
GETGet a specific season/seasons/{id}
GETGet a specific episode/episodes/{id}
GETGet a specific network/networks/{id}
GETGet a specific media asset/media_assets/{id}
GETGet a specific classification/classifications/{id}
GETGet a specific classification inclusion/classification_inclusions/{id}
GETGet the episode released right after the specified one/episodes/{id}/next_sibling
GETGet the episode released right before the specified one/episodes/{id}/previous_sibling

How automating ART19 Content Documentation works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live ART19 Content Documentation account.
Grant access, then go live. You approve the specific ART19 Content Documentation operations it may use — and only those.