Automate Digitallinguistics DLx
HumDay reads Digitallinguistics DLx’s own published API description and derives 18 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 Digitallinguistics DLx is
The Digital Linguistics (DLx) REST API
API host: api.digitallinguistics.io
What HumDay can do in Digitallinguistics DLx
12 documented operations change something in Digitallinguistics DLx.
- POSTAdd a new Lexeme
/lexemes - POSTAdd a new Language
/languages - PUTUpsert (add or replace) a Lexeme
/lexemes - PUTUpsert (create or replace) a Language
/languages - POSTAdd a new Lexeme to a Language
/languages/{languageID}/lexemes - PUTUpsert (add or replace) a Lexeme
/languages/{languageID}/lexemes - DELETEDelete a Lexeme by ID
/lexemes/{lexemeID} - PATCHPerform a partial update on a Lexeme
/lexemes/{lexemeID} - DELETEDelete a Language by ID
/languages/{languageID} - PATCHPerform a partial update on a Language
/languages/{languageID} - DELETEDelete a Lexeme by ID
/languages/{languageID}/lexemes/{lexemeID} - PATCHPerform a partial update on a Lexeme
/languages/{languageID}/lexemes/{lexemeID}
What HumDay can read from Digitallinguistics DLx
These are the operations a schedule or a trigger can watch.
- GETGet all Lexemes
/lexemes - GETGet all Languages
/languages - GETGet a Lexeme by ID
/lexemes/{lexemeID} - GETRetrieve a Language by ID
/languages/{languageID} - GETGet all Lexemes for a Language
/languages/{languageID}/lexemes - GETGet a Lexeme by ID
/languages/{languageID}/lexemes/{lexemeID}
How automating Digitallinguistics DLx 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 Digitallinguistics DLx account.
- Grant access, then go live. You approve the specific Digitallinguistics DLx operations it may use — and only those.
Automate Digitallinguistics DLx with these
- OpenAI273 operations
- MotaWord219 operations
- Anthropic144 operations
- Contract P Contract.fit134 operations
- NamSor84 operations
- Salesforce Einstein Vision and Einstein Language45 operations
- Semantria41 operations
- FunTranslations36 operations
- Formapi35 operations
- Handwrytten30 operations
- Neutrinoapi Neutrino27 operations
- Oxforddictionaries Oxford Dictionaries26 operations
Categories
Questions about Digitallinguistics DLx automation
- Can HumDay connect to Digitallinguistics DLx?
- Yes. HumDay reads Digitallinguistics DLx's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 18 operations are documented.
- Do I need to write code to automate Digitallinguistics DLx?
- 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 Digitallinguistics DLx account.
- What can HumDay do in Digitallinguistics DLx?
- 12 of the 18 documented operations change something in Digitallinguistics DLx, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Digitallinguistics DLx 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 Digitallinguistics DLx is held behind that approval.
Where this came from
The operations above are read from a published API description for Digitallinguistics DLx at raw.githubusercontent.com/digitallinguistics/api/master/public/swagger/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.