Behind the scenes
Six different Connect API endpoints are queried to provide Connect content and user information. This information is deployed to Connect as 6 different pins. These pins are generated by a R Markdown script deployed on Connect, and updated on a prescribed interval using Connect's scheduling engine. The 6 pins / API endpoints are:
| Connect API Endpoint | connectapi
function | Pin | Description | Pin retrieval |
|----------------------|-----------------------|----------------------|-------------------------------------------------------|------------------------------------------------------|
| GET /v1/groups
| get_groups
| Group Info | List local groups | pin_read(board, "katie/group-info")
|
| GET /v1/users
| get_users
| User Info | List local users | pin_read(board, "katie/user-info")
|
| GET /v1/content
| get_content
| Content Info | List all content items visible to the requesting user | pin_read(board, "katie/content-info")
|
| GET /v1/instrumentation/content/visits
| get_usage_static()
| Non-Shiny Content Visit Counts | Get instrumentation data for non-Shiny content | pin_read(board, "katie/nonshiny-usage"
|
| GET /v1/instrumentation/shiny/usage
| get_usage_shiny()
| Shiny App Usage | Get instrumentation data for Shiny content | pin_read(board, "katie/shiny-usage"
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.