Developer documentation

journy.io developers.journy.io

# Welcome Implementing a new tool can be daunting, but it doesn't have to. You can implement journy.io in a few different ways to ensure it fits with the rest of your tech stack seamlessly. We welco

does kind undeclared Customer Service · inferred probed 3/6 apis.guruapitracker.io (sitemap 2020-10)

Coordinates in the economy

Capability: deleteAccountupsertAccountaddUserToAccountremoveUserFromAccountgetEventstrackJourneyEvent · hints, unresolved
Function: Customer Service
Register key: fn-customer-service (inferred)
Class: does · performs an act when called · inferred
NAICS node: 513210 · national-industry · inferred (sourceCategory:customer_relation)
Ruled name: unclaimed at this grain
Occupations: —
Records: —

Customer Service — one of 53 categories on the board (verticals above, functions below).

Every offering binds one capability (the provider-independent resource) to one provider, and resolves to one category of the register board — the vertical it serves or the function it performs, with the occupations whose work it carries and the records it keeps. Browsing the directory is browsing the economy graph.

Machine face

# this entry, as data
curl https://apis.directory/apis/journyio/apisguru-journy.io.json

# the whole register
curl https://apis.directory/index.json