Producer Tasks Vs. Customer Tasks

This section provides an overview of the tasks that a producer, administrator or client application perform and the corresponding APIs. The task numbers refer to the corresponding tasks in the diagram below the table:

Producer tasks vs. customer tasks
Persona	Activity	Method	Path
Producer	Implement software to request use of items valid in the rate table, for which tokens will be charged	N/A	N/A
	Create rate table (task 1)	POST	/provisioning/api/v1.0/rate-tables
	View instances (task 2)	GET	/provisioning/api/v1.0/instances
	View line items (task 3)	GET	/provisioning/api/v1.0/instances/{instanceId}/line-items
	Map line items to an instance (intended for producers who do not use FlexNet Operations as their back office)	PUT	/provisioning/api/v1.0/instances/{instanceId}/line-items
	Monitor usage data (task 4)		Data Access APIs, Analytics Dashboard, or Snowflake data query
Administrator of customer organization	Obtain instance ID from producer (task 5)	N/A	N/A
	View line items on the instance (task 6)	GET	/provisioning/api/v1.0/instances/{instanceId}/line-items
	Delete sessions to tidy up (if client application hasn’t deleted sessions) (task 7)	DELETE	/api/v1.0/sessions/{sessionId}
	Track live sessions and their status (task 8)	GET	/api/v1.0/sessions/{instanceId}
End user of client application	Run the client application.	N/A	N/A
Client application	One-off access request for use of items (task 9)	POST	/elastic/api/v1.0/instances/{instanceId}/access-request
	Create a session on its instance (task 10)	POST	/api/v1.0/sessions
	Request use of items in a session (task 11)	PUT	/api/v1.0/sessions/{sessionId}
	Send heartbeat to the session (task 12)	GET	/api/v1.0/sessions/{sessionId}/heartbeat
	Delete the session (task 13)	DELETE	/api/v1.0/sessions/{sessionId}

The following diagram visually separates the tasks, depending on the persona that actions them:

Tasks performed by the producer, customer administrator and client application