INN002 - How to Interpret an API: From Start to Working Code - Salvatore Colangelo

Document created by communitymanager on Jun 2, 2017Last modified by User16087 on Aug 2, 2017
Version 4Show Document
  • View in full screen mode

Salvatore Colangelo (Goya Pty Ltd)

Session Description

FileMaker has all the tools you need to integrate with Web Services—but how to get started?

 

In this session, we’ll examine examples of external APIs that users want to build into a FileMaker solution: what to look for in the documentation, how you convert that into FileMaker code, and how to build a real working example.

 

This walkthrough session will look at each of the steps, defining a framework applicable to most of the modern web APIs.

What you should know

Basic knowledge of web technologies, the FileMaker Platform, scripting and custom functions.

Products & Technologies

  • Pro/Advanced
  • Go
  • Server

Session Materials

  • Please see the attachment(s) below.
  • I've uploaded the two demo files. Some notes:
    • for the Stripe example you will need to create a Stripe account (test data) and copy and paste the Stripe Secret (the API key) in the custom function in FileMaker
    • for the FM mugshot example you will need API keys from AWS and from the Cognitive Services Face API and copy/paste them in the matching custom functions. I'm writing an article for the Goya blog regarding the AWS signature
    • the logic behind FM mugshot is this: you pre-load a set of faces to the web service (your reference faces) and then every time you try to log in you try to match the new photo against the reference ones. So the first step to test the file is to create some records in the Faces tables and run the Preload script, so that the web service can create its reference list

What You Will Learn

  • Understand the API language/documentation
  • Creating JSON inputs and parsing outputs
  • Test cases for the basic operations
  • A framework to apply in the real world

Attachments

Outcomes