Automate ID4i

What ID4i is

ID4i HTTP API

What HumDay can do in ID4i

51 documented operations change something in ID4i. The 49 most useful are listed here.

• POSTAdd history item/api/v1/history/{id4n}
• POSTRegister user/account/registration
• POSTCreate GUID(s)/api/v1/guids
• POSTCreate API key/api/v1/apikeys
• POSTCreate collection/api/v1/collections
• POSTCreate organization/api/v1/organizations
• POSTID4i API Login/login
• POSTCreate an document for an id4n/api/v1/documents/{id4n}/{organizationId}
• POSTAdd role(s) to user/api/v1/organizations/{organizationId}/users/{username}/roles
• POSTRequest password reset/account/password
• PUTVerify password reset/account/password
• PUTComplete registration/account/registration
• POSTVerify registration/account/verification
• PUTStore routing file/api/v1/routingfiles/{id4n}
• POSTInvite Users/api/v1/organizations/{organizationId}/users/invite
• POSTAdd privilege/api/v1/apikeys/{key}/privileges
• POSTAdd elements to collection/api/v1/collections/{id4n}/elements
• POSTImport GS1/MAPP codes/api/v1/import/gs1
• PUTAdd partner/api/v1/organizations/{organizationId}/partner
• PUTPut an document for an id4n/api/v1/documents/{id4n}/{organizationId}
• DELETERemove role(s) from user/api/v1/organizations/{organizationId}/users/{username}/roles
• PATCHChange GUID information./api/v1/guids/{id4n}
• DELETEDelete API key/api/v1/apikeys/{key}
• PUTUpdate API keys/api/v1/apikeys/{key}
• DELETEDelete collection/api/v1/collections/{id4n}
• PATCHUpdate collection/api/v1/collections/{id4n}
• POSTAdd alias for GUID or Collection/api/v1/id4ns/{id4n}/alias/{aliasType}
• DELETEDelete organization/api/v1/organizations/{organizationId}
• PUTUpdate organization/api/v1/organizations/{organizationId}
• POSTEnqueue a custom message/api/v1/organizations/{organizationId}/messaging/enqueueCustomMessage
• DELETEDelete ID4n properties/api/v1/id4ns/{id4n}/properties
• PATCHPatch ID4n properties/api/v1/id4ns/{id4n}/properties
• DELETERemove privilege/api/v1/apikeys/{key}/privileges
• PUTPrepare an object for transfer/api/v1/transfers/{id4n}/sendInfo
• DELETERemove elements from collection/api/v1/collections/{id4n}/elements
• PUTTransfer a GUID or collection, obtaining it (i.e./api/v1/transfers/{id4n}/receiveInfo
• DELETEDelete a document/api/v1/documents/{id4n}/{organizationId}/{fileName}
• PATCHUpdate history item/api/v1/history/{id4n}/{organizationId}/{sequenceId}
• DELETEDelete organization logo/api/v1/organizations/{organizationId}/logo
• POSTUpdate organization logo/api/v1/organizations/{organizationId}/logo
• POSTAdd ID4ns of a privilege/api/v1/apikeys/{key}/privileges/{privilege}/id4ns
• DELETERemove partner/api/v1/organizations/{organizationId}/partner
• PUTWrite data to microstorage/api/v1/microstorage/{id4n}/{organization}
• PATCHUpdate a document/api/v1/documents/{id4n}/{organizationId}/{fileName}/metadata
• PUTSet history item visibility/api/v1/history/{id4n}/{organizationId}/{sequenceId}/visibility
• DELETERemove aliases from GUID or Collection/api/v1/id4ns/{id4n}/alias/{aliasType}
• PUTStore address/api/v1/organizations/{organizationId}/addresses/default
• DELETERemove id4ns of a privilege/api/v1/apikeys/{key}/privileges/{privilege}/id4ns
• PATCHUpdate messaging/api/v1/organizations/{organizationId}/messaging

What HumDay can read from ID4i

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

• GETList roles/api/v1/roles
• GETFind users/api/v1/users
• GETList countries/api/v1/countries
• GETList all supported alias types/api/v1/search/guids/aliases/types
• GETList users and their roles/api/v1/organizations/{organizationId}/roles
• GETSearch for GUIDs by alias/api/v1/search/guids
• GETList all privileges/api/v1/apikeys/privileges
• GETRetrieve organizations of user/api/v1/user/organizations
• GETList history/api/v1/history/{id4n}
• GETList documents/api/v1/documents/{id4n}
• GETFind by username/api/v1/users/{username}
• GETRetrieve routing file/api/v1/routingfiles/{id4n}
• GETForward/go/{guid}
• GETResolve owner of id4n/whois/{id4n}
• GETRetrieve version information about ID4i/api/v1/info
• GETFind API key by organization/api/v1/apikeys
• GETList public documents/api/v1/public/documents/{id4n}
• GETList privileges/api/v1/apikeys/{key}/privileges
• GETList contents of the collection/api/v1/collections/{id4n}/elements
• GETFind users in organization/api/v1/organizations/{organizationId}/users
• GETList change log entries of an organization/api/v1/changelog/organization/{organizationId}/
• GETList my privileges/api/v1/organizations/{organizationId}/privileges
• GETRetrieve GUIDs not in any collection/api/v1/guids/withoutCollection
• GETList organization specific documents/api/v1/documents/{id4n}/{organizationId}
• GETGet user roles by username/api/v1/organizations/{organizationId}/users/{username}/roles
• GETRetrieve GUID information/api/v1/guids/{id4n}
• GETRetrieve ID4n information/api/v1/id4ns/{id4n}
• GETShow API key/api/v1/apikeys/{key}
• GETFind collection/api/v1/collections/{id4n}
• GETGet multiple ID4n properties/api/v1/multiple/id4ns/properties
• GETFind organization by id/namespace/api/v1/organizations/{organizationId}
• GETGet all aliases for the given GUID or Collection./api/v1/id4ns/{id4n}/alias
• GETRetrieve all public routes for a GUID/api/v1/public/routes/{id4n}
• GETShows the public history of the given GUID/api/v1/public/history/{id4n}
• GETResolve image/api/v1/public/image/{imageID}
• GETRetrieve ID4n properties/api/v1/id4ns/{id4n}/properties
• GETRetrieve collections of an ID/api/v1/id4ns/{id4n}/collections
• GETShow transfer preparation information/api/v1/transfers/{id4n}/sendInfo
• GETRead document contents/api/v1/documents/{id4n}/{organizationId}/{fileName}
• GETGet history item/api/v1/history/{id4n}/{organizationId}/{sequenceId}
• GETRead public organization information/api/v1/public/organizations/{organizationId}
• GETGet partners of an organization/api/v1/organizations/{organizationId}/partner
• GETGet collections of organization/api/v1/organizations/{organizationId}/collections
• GETRead data from microstorage/api/v1/microstorage/{id4n}/{organization}
• GETRead public document contents/api/v1/public/documents/{id4n}/{organizationId}/{fileName}
• GETRetrieve a document (meta-data only, no content)/api/v1/documents/{id4n}/{organizationId}/{fileName}/metadata
• GETRetrieve current route of a GUID (or ID4N)/api/v1/routingfiles/{id4n}/route/{type}
• GETRetrieve address/api/v1/organizations/{organizationId}/addresses/default
• GETRetrieve all routes of a GUID (or ID4N)/api/v1/routingfiles/{id4n}/routes/{type}
• GETRetrieve a public document (meta-data only, no content)/api/v1/public/documents/{id4n}/{organizationId}/{fileName}/metadata
• GETID4ns of a privilege/api/v1/apikeys/{key}/privileges/{privilege}/id4ns

How automating ID4i works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. 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.
3. See it proven. The program runs and shows you the result before it is allowed near your live ID4i account.
4. Grant access, then go live. You approve the specific ID4i operations it may use — and only those.

Automate ID4i with these

• NetBox844 operations
• Mist768 operations
• Loket.nl641 operations
• DocuSign414 operations
• Osisoft PI 2018 SP1 Swagger Spec413 operations
• Meraki Dashboard263 operations
• Pipedrive196 operations
• Akeneo PIM140 operations
• Apache Superset120 operations
• Neblio Suite50 operations
• TYK Gateway18 operations
• Personio Personnel Data13 operations

Categories

• Enterprise

Questions about ID4i automation

Can HumDay connect to ID4i?

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

Do I need to write code to automate ID4i?

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 ID4i account.

What can HumDay do in ID4i?

51 of the 106 documented operations change something in ID4i, and 55 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my ID4i 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 ID4i is held behind that approval.

Where this came from

The operations above are read from a published API description for ID4i at backend.id4i.de/docs/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.