DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Data Engineering
  3. Databases
  4. Resource-Centric API Calls: Switching Up the Cloud Elements Hubs

Resource-Centric API Calls: Switching Up the Cloud Elements Hubs

In Cloud Elements' platform for API integration, developers can now define their own API resources, accessed by a consistent RESTful API with a JSON payload.

Ross Garrett user avatar by
Ross Garrett
·
Apr. 28, 17 · News
Like (1)
Save
Tweet
Share
7.48K Views

Join the DZone community and get the full member experience.

Join For Free

our api hubs represent the intersection of resources across the elements within a category of applications. we created a platform for api integration with the assumption that one-to-many means that integrating to many crms (or finance apps, or marketing automation platforms) is faster than building one-by-one. however, something new we have learned is that our customers are using integrations beyond the category. we're excited to announce resource-center api calls for developers to define their own api resources.

api developer documentation

we now support api calls directly to resources, without requiring association to a hub. previously, if you wanted to call get /contacts to salesforce, the entire api would have to look like:  get /hubs/crm/contacts. the requirement to know the hub for all the elements you were using caused problems for some use cases.

now, you can call get /contacts directly without specifying a hub.  this will provide multiple benefits, including:

  • resources are now accessible regardless of the hub each element resides.
  • one-to-many integrations are simpler since you no longer need to know the hub location for an element.
  • lays the groundwork for composite resources and composite hubs, such as what inspirato did to orchestrate data in their app .

api call get company every resource is accessed using a consistent restful api with a json payload, regardless of the api protocol used at the endpoint. cloud elements’ pre-built connectors do the work of mapping the unified api call to each provider’s api endpoint, as well as transforming soap, xml and other api protocols to rest/json.  when cloud elements creates an element, the resources defined for that element are normalized to the intersection of resources that are available across the applications in that category.

for example, a user can create a common object for use across hubs, which could be a company object. the individual application endpoints may use different naming conventions for this resource, such as account in salesforce, company in hubspot, and organization in quickbooks. cloud elements resource normalization transforms all varieties of the company object to one uniform model.

using resource-centric api calls, the common objects will still be normalized even though they do not need to be associated with the hub within the call.

for more information on our hubs and elements, check out our api documentation .

Element API Cloud

Published at DZone with permission of Ross Garrett, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Simulate Network Latency and Packet Drop In Linux
  • Educating the Next Generation of Cloud Engineers With Google Cloud
  • Fraud Detection With Apache Kafka, KSQL, and Apache Flink
  • Do Not Forget About Testing!

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: