Automate IX API IX

What IX API IX is

This API allows to config/change/delete Internet Exchange services. # Filters When querying collections, the provided query parameters are validated. Unknown query parameters are ignored. Providing invalid filter values should yield a validation error.

What HumDay can do in IX API IX

35 documented operations change something in IX API IX.

• POSTCreate a new contact./contacts
• POSTReauthenticate the API user, issue a new accesstoken and refreshtoken pair by providing the refreshtoken in the request body./auth/refresh
• POSTCreate a new account./accounts
• POSTCreate a new network service/network-services
• DELETERemove a contact. Please note, that a contact can only be removed if it is not longer in use in a network service or config through a role assignment./contacts/{id}
• PATCHUpdate parts of a contact/contacts/{id}
• PUTUpdate a contact/contacts/{id}
• POSTAdd an ip host address or network prefix./ips
• POSTAssign a Role to a Contact./role-assignments
• POSTCreate a member joining rule/member-joining-rules
• POSTCreate a configuration for a NetworkFeature defined in the NetworkFeatures collection./network-feature-configs
• POSTCreate a network-service-config./network-service-configs
• POSTAuthenticate an API user identified by apikey and apisecret./auth/token
• POSTRegister a mac address./macs
• DELETERemove a role assignment from a contact./role-assignments/{assignment_id}
• PATCHUpdate parts of an ip address./ips/{id}
• PUTUpdate an ip address object./ips/{id}
• DELETERemove a mac address./macs/{id}
• DELETEAccounts can be deleted, when all services and configs are decommissioned or the account is not longer referenced e.g./accounts/{id}
• PATCHUpdate parts of an account./accounts/{id}
• PUTUpdate the entire account./accounts/{id}
• DELETERequest decomissioning of the network service./network-services/{id}
• PATCHPartially update a network service/network-services/{id}
• PUTUpdate a network service/network-services/{id}
• DELETEDelete a joining rule/member-joining-rules/{id}
• PATCHPartially update a joining rule/member-joining-rules/{id}
• PUTUpdate a joining rule/member-joining-rules/{id}
• DELETERemove a network feature config./network-feature-configs/{id}
• PATCHUpdate parts of a network feature configuration/network-feature-configs/{id}
• PUTUpdate a network feature configuration/network-feature-configs/{id}
• DELETERequest decommissioning the network service configuration./network-service-configs/{id}
• PATCHUpdate parts of an exisiting network-service-config./network-service-configs/{id}
• PUTUpdate an exisiting network-service-config/network-service-configs/{id}
• DELETERetract or reject a change to the network service./network-services/{id}/change-request
• POSTRequest a change to the network service./network-services/{id}/change-request

What HumDay can read from IX API IX

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

• GETList all mac addresses managed by the authorized customer./macs
• GETList available contacts managed by the authorized account./contacts
• GETList all role assignments for a contact./role-assignments
• GETGet a contact by it's id/contacts/{id}
• GETList all ip addresses (and prefixes)./ips
• GETList all PoPs/pops
• GETList all ports./ports
• GETList all roles available./roles
• GETList available devices/devices
• GETRetrieve a list of Accounts./accounts
• GETGet a (filtered) list of facilities./facilities
• GETList all connections./connections
• GETList all MetroAreas/metro-areas
• GETList available network features./network-features
• GETList available NetworkServices./network-services
• GETList all (filtered) products-offerings available on the platform/product-offerings
• GETList all MetroAreaNetworks/metro-area-networks
• GETGet a list of joining rules/member-joining-rules
• GETGet the IX-API service health status./health
• GETGet a role assignment for a contact./role-assignments/{assignment_id}
• GETGet the API implementation details./implementation
• GETGet all network feature configs./network-feature-configs
• GETGet all network-service-configs./network-service-configs
• GETGet a single ip addresses by it's id./ips/{id}
• GETThe cancellation-policy can be queried to answer the questions: If I cancel my subscription, when will it be technically decommissioned?/network-service-configs/{id}/cancellation-policy
• GETGet a single mac address by it's id./macs/{id}
• GETGet a single point of presence/pops/{id}
• GETRetrieve a port./ports/{id}
• GETGet a single Role./roles/{id}
• GETGet a specific device identified by id/devices/{id}
• GETGet a single account./accounts/{id}
• GETRetrieve a facility by id/facilities/{id}
• GETRead a connection./connections/{id}
• GETGet a single MetroArea/metro-areas/{id}
• GETGet a single network feature by it's id./network-features/{id}
• GETGet a specific network-service by id./network-services/{id}
• GETGet a single products-offering by id./product-offerings/{id}
• GETRetrieve a MetroAreaNetwork/metro-area-networks/{id}
• GETGet a single rule/member-joining-rules/{id}
• GETGet a single network feature config./network-feature-configs/{id}
• GETGet a network-service-config/network-service-configs/{id}
• GETGet the change request./network-services/{id}/change-request
• GETThe cancellation-policy can be queried to answer the questions: If I cancel my service, when will it be technically decommissioned?/network-services/{id}/cancellation-policy

How automating IX API IX 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 IX API IX account.
4. Grant access, then go live. You approve the specific IX API IX operations it may use — and only those.

Automate IX API IX with these

• Cloudflare3122 operations
• N Auth nextAuth55 operations
• Conjur41 operations
• Credas37 operations
• Cisco PSIRT openVuln19 operations
• Users (Okta )19 operations
• 1Password Connect15 operations
• CyCAT.org14 operations
• Swagger for Patrowl Engines14 operations
• Appspot Authentiq12 operations
• Testfire AltoroJ12 operations
• hashlookup CIRCL11 operations

Categories

• Security

Questions about IX API IX automation

Can HumDay connect to IX API IX?

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

Do I need to write code to automate IX API IX?

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 IX API IX account.

What can HumDay do in IX API IX?

35 of the 78 documented operations change something in IX API IX, and 43 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Where this came from

The operations above are read from a published API description for IX API IX at docs.ix-api.net/v2/ix-api-latest.json. Descriptions are the provider’s own words, not ours. Last published 2021-08-16.