The MarTech Digest
548.5K views | +50 today
Follow
Your new post is loading...
Scooped by CYDigital/marteq.io
Scoop.it!

The State of APIs: a cheat-sheet infographic - Get Elastic

The State of APIs: a cheat-sheet infographic - Get Elastic | The MarTech Digest | Scoop.it
Leading industry research firm, Gartner Inc., recognized API-based commerce platforms as the next-gen category of commerce evolution. But not all APIs are
CYDigital/marteq.io's insight:

marketingIO’s MarTech Managed Services solves numerous B2B Marketing challenges. Contact us to see how. #MarTech #DigitalMarketing

more...
No comment yet.
Scooped by CYDigital/marteq.io
Scoop.it!

What is GraphQL and why should you care? The future of APIs - Enterprise Irregulars

What is GraphQL and why should you care? The future of APIs - Enterprise Irregulars | The MarTech Digest | Scoop.it
GraphQL is an open source technology created by Facebook that is getting a fair bit of attention of late. It is set to make a major impact on how APIs are designed. GraphQL is primarily about designing your APIs more effectively, and being more specific about access to your data sources.

So what about Facebook? It built GraphQL because it needed something powerful enough to describe Facebook’s API structure, but easy to learn by mobile developers. It is seeing billions of API calls a day now, so we know it scales. As Facebook points out, the shape of the query mirrors the shape of the response, which is cool.

In summary GraphQL maps pretty well to new API-driven models such as serverless. Michael Unger from Neo4j feels REST is worth retiring. That said, technologies don’t die overnight. REST is hardly going to disappear overnight. But for a class of problems for high scale sites it’s we’re going to see significant adoption of GraphQL. Google Trends shows growing interest in GraphQL and gRPC. GraphQL maps to external consumption of APIs, with gRPC for internal. They’re both clearly spiking in interest.
CYDigital/marteq.io's insight:

An excellent backgrounder on GraphQL.

 

RYZZ is coming. It’s a new approach to MarTech for B2B Marketers.

#MarTech #DigitalMarketing

more...
No comment yet.
Scooped by CYDigital/marteq.io
Scoop.it!

How to Use an API: Just the Basics - TechnologyAdvice

How to Use an API: Just the Basics - TechnologyAdvice | The MarTech Digest | Scoop.it
An API is useful for pulling specific information from another program. If you know how to read the documentation and write the requests, you can get lots of great data back, but it may be overwhelming to parse all of this. That’s where developers come in. They can build programs that display data directly in an app or browser window in an easily consumable format.

CYDigital/marteq.io's insight:

A brief primer when you CT...

 

Dark marketing clouds ahead? Let us help you see clearly. Contact us. #MarTech #DigitalMarketing

more...
No comment yet.
Scooped by CYDigital/marteq.io
Scoop.it!

What is Swagger and Why it Matters - ReadMe

Swagger (okay, now the "Open API Initiative"... more on that later!) is a framework for describing your API using a common language that everyone can understand. Think of it as a blueprint for a house. You can use whatever building materials you like, but you can't step outside the parameters of the blueprint.

There are other available frameworks that have gained some popularity, such as RAML, APIBlueprint, and Summation. But Swagger provides more benefits than just helping create clear documentation.

  • It's comprehensible for developers and non-developers. Product managers, partners, and even potential clients can have input into the design of your API, because they can see it clearly mapped out in this friendly UI.
  • It's human readable and machine readable. This means that not only can this be shared with your team internally, but the same documentation can be used to automate API-dependent processes.
  • It's easily adjustable. This makes it great for testing and debugging API problems.
CYDigital/marteq.io's insight:

If not applicable to you, then please pass it on to your MarkOps person/crew.

 

NEW: Experience Remarkable Planning Accuracy With New, FREE Growth Hacking Tool. Go here: http://goo.gl/UjcA8x  

more...
No comment yet.
Scooped by CYDigital/marteq.io
Scoop.it!

5 Things CMOs Need To Know About APIs - MarketingLand

5 Things CMOs Need To Know About APIs - MarketingLand | The MarTech Digest | Scoop.it

Digest...


1.  Be Where Your Customers Are, No Matter What The Channel

The notion of gaining access to all those devices is daunting. Luckily, there’s a fast-track solution. APIs let you securely serve up your data, services, or content, enabling developers to build apps for any device using that data.

 

2. Partnering For Digital Network Effects

APIs make it easy to exchange data and integrate with partners. Your partners, in turn, can extend the value of your data and create something even more valuable.

 

3. In The Digital Economy, Innovation Happens Outside Your Box

APIs not only let you showcase your business on mobile devices and create network effects with partners to fuel innovation. They open up access to millions of app developers around the world who are hungry to build the next big thing.

 

4. Survival Of The Fastest

APIs are the business technology that removes organizational, technical, and security barriers to unlock the value inside your enterprise. They make it easier for a CIO to say “yes” to a CMO while maintaining security and control. They’re a simple interface on complex systems that provides the agility to react when market and customer expectations shift.

 

5. Become A Real Digital Business

CMOs need to understand how new technologies like APIs help create value for customers. CIOs need to understand how customer and market expectations must drive their technology decisions. In other words, the partnership must center around the customer.

 

Receive a FREE daily summary of The Marketing Technology Alert

CYDigital/marteq.io's insight:

For homegrown systems, APIs open up your finely built engine to a variety of functions from 3rd parties. So don't exclude the legacy systems: APIs take internal systems to much higher levels.

more...
No comment yet.