Support cookbook recipes in connectapi: Integrations & Sessions

[toph-allen]

Recipes:

• Associate Integrations to Content
• Creating Integrations
• Deleting All Sessions for an Integration
• Deleting Integrations
• Deleting Sessions
• Finding Content Associated with an Integration
• Finding Integrations Associated to Content
• Finding Integrations
• Finding Sessions
• Removing Integration Associations from Content
• Updating Integrations
• Viewing Integration Information
• Viewing Session Information

Integrations and Sessions are CRUD objects so should be treated as a resource class.

The associated endpoints:

PUT "v1/content/", CONTENT_GUID, "/oauth/integrations/associations" (empty body removes integration associations)
POST, GET "v1/oauth/integrations"
GET "v1/oauth/sessions/"
DELETE “v1/oauth/sessions/{session$guid}”

Content Item Endpoints

These should be methods on the content item

• Endpoints:
  • List all OAuth integration associations
  • Set all OAuth integration associations (for the delete recipe)

OAuth Integrations Endpoints

These are all the interactions from the perspective of the API.

• List integrations
• Create an integration
• Get integration details
• Delete an integration
• Update an integration
• List all associations

Need to bother with templates?

OAuth Sessions

Primary interactions:

• List sessions
• Get session details
• Delete a session

OAuth session class should fit the schema.

Notes

• OAuth integrations & content. Will we need a template object? The return value Integration wants to be a type.
• Creating an integration:

Other

• The recipes e.g. "Associate integrations with content" should probably go under the Integrations subhead.