Tagged: API

Using The AvantLink API To Streamline Your Affiliate Efforts

Justin Ball

Lamborghini

It Would Be Really Cool If...

Open All The Things!

Open All The Things

  • Open Source
  • APIs
  • Open Content

Open Source

Canvas LTI screenshot

  • Moved from installs to services
  • Developers read the code. Create better integrations
  • Result is a healthy community of applications

Open Content

  • Kahn Academy
  • MIT Open Courseware
  • Creative Commons

Users win with cool remixes

Organizations (and professors) win with brand recognition

APIs

Symbiotic Relationship

Developers imagine new features for your platform.

Platform wins new functionality and profits.

Developer wins large audience and profits.

<Begging>

Please implement OAuth

Everyone else is doing it

and standards make things easy

</Begging>

Cool Story Bro

The AvantLink API

AvantLink API documentation screenshot

Merchant API

AvantLink API documentation merchant screenshot

Ignore This

Affiliate API

AvantLink API documentation affiliate screenshot

Affiliate API

AvantLink API documentation affiliate screenshot

The AvantLink API

Continue Reading →

Authorize.net – User authentication failed due to invalid authentication values

So you've worked hard to integrate your website with authorize.net and now you're ready to turn it on and make the big bucks. You run your first real transaction and get:

User authentication failed due to invalid authentication values. code="E00007"

or

This account has not been given the permission(s) required for this request.

or

E00007 User authentication failed due to invalid authentication values

You pull your hair out. You swear a lot. Then you calm down. Log into your Authorize.net account and get click on "API Login ID and Transaction Key". You probably used your login and password to access the gateway. Use the api login and key and you are good to go.

UPDATE: As Kerry pointed out you might also want to make sure you aren't pointed at the test gateway. Your production credentials won't do you any good there.

Continue Reading →

FamilySearch Developer Webinar

I just got an invite to a FamilySearch Webinar. I imagine you are supposed to be a member of the developer group to attend, but I doubt they would throw you out. Here's the details:

FamilySearch Developer WebinarJoseph Smith Memorial Building (JSMB) 5th Floor, West Lobby Conference Room 3:00 PM - 4:00 PM

Agenda:

  • Introduce Robert Kehrer and Jimmy Zimmerman
  • Changes to DevNet.FamilySearch.org (Gordon)
  • Use of API Reference System (Gordon)
  • Next Beta May 5th (Gordon)
  • Selectable Summary (Jimmy)
  • Read Citations (Jimmy)
  • Questions and Answers

Continue Reading →

Family Tree Read

What do we read out of family search?

  • Person Information
  • Search Match
  • Authorities Data - places
  • LDS Ordinance Information

Objects available in the new FamilySearch

  • Person
  • Search Data
  • Contributor Information
  • Place Standardization Data

Can output XML, JSON, and XML-FastInfoset. Request can be gzipped if client supported.

Locate a resource via NFS Id - 'KWCD-QBC', Ancestral File Number - 'afn.2bW3-9H' or Gedcom UID.

Examples:

https://api.familysearch.org/familytree/v1/person/KWCD-QBC?sessionId=MMMM

https://api.familysearch.org/authorities/v1/place/933423?sessionId=MMMM

https://api.familysearch.org/v1/search?name=Isreal Hoyt heaton?sessionId=MMMM

Get the schema:

Continue Reading →

Family Search API

If these posts don't make sense sorry. They are for my notes.

API is based on REST. A lot of data is sensitive so they use SSL to secure data transfer. Prefer XML elements over XML attributes. Everything is UTF-8 encoded. Right now user access is limited to LDS members. That is interesting. I guess you have to have a membership number so that you can access the API, but they will change that over time.

They need to go faster. This is all pretty bla so far.

Query looks like this:

https://api.familysearch.org/{module}/{version}/{endoint}/{id}

You need a developer key. Keys are tied to individuals so they can get a hold of you when you break something.

Login like this:

https://api.familysearch.org/identity/v1/login?key=MMMM-MMMM-MMMM-MMMM-MMMM-MMMM-MMMM-MMMM

You will have to sign an agreement to get a key.

After you authenticate you get a session key which you then have to pass back on each request. They give you back xml for each request.

It looks like you have to send an email and j...

Continue Reading →

Ruby fs-api

I am in the Ruby-fs API presentation now. Funding for the library came from USFamilyTree.com.

It is REST based.

Data model is: Person Person has many Assertions Assertion has one Contributor, Citation(not yet implemented), Note

Each person has a lot of data associated with them so you don't want to be parsing xml data on the fly.

Include the library with this: require 'family_tree_api/client'

The library will handle turning all the data into objects for you. This makes access to the API slick. I love ruby. ie

 person = client.summary_person 'KW3B-2L7', descendants => 2 mother = person.mother grandmother = person.mother.mother 

 search_params = {:givenName => 'Parker', :familyName => 'Flech'} results = client.search search_params 

As with all things Ruby this API makes it very easy to talk to FamilySearch. If you are in the genealogy space and know Ruby give it a try.

The good news is that they are open to patches. The project is in active de...

Continue Reading →

Family Search Write

We're back from lunch. I had a great chat with Alan Braverman the CTO & founder of Geni. They are doing some cool things by connecting living people with their families and to the larger family graph. They also let you upload photos and other digital assets then assemble that into a timeline. Eventually you will be able to create a family timeline.

On to the FamilyTree Write. This part of the API seems to be mainly applicable to software packages that want to contribute data to FamilySearch. I am more of a data mooch than a data provider so it isn't as interesting but here goes:

Only the assertions section of the entry is writable. In version 1.1 the summary section will be writable. Only the assertion value can be changed. ie you can't just change the date of an event. You have to change all parts of the event - the date, the place, the type (birth, death, etc) and the description. If you left out the place or type it would update the date and delete the place and type...

Continue Reading →

Creative Commons Opens Legal Documents

A couple of developers from Creative Commons were at the code sprint last week. It is fun to interact with guys who are making the world a better place. Creative Commons latest move was to make it easy to get to 1.8 million pages of case law. Here's some more information and ReadWriteWeb.. This could be a fun API to use in some future project.

Continue Reading →