glip | Geographic Location for IP Address with MaxmindDB | TCP library

To share an attachment via the Glip API, create a new post with an existing attachment.

Create Post API

The Create Post API takes an optional attachments array which references existing attachments. Both the id and type properties are required. Both properties are present in the post API response.

Instead of using the path parameter, use the query string parameter as follows. Here, groupId is the same as the chatId in the question above.

• https://app.glip.com/chat/r?groupid={groupId}

Both the bot name and bot icon in Glip can be updated via the Update Extension API using the bot's access token if the bot app has the EditExtensions permission.

Update Bot Name via Update Extension API

The Update Extension Info API can be used by the bot to update the bot's name in Glip if the bot has the EditExtensions app permission. The bot's name in Glip will be updated to reflect this in real-time.

This is an example HTTP request.

The Compliance Exports API requires the authorized user be a Glip Administrator with the Compliance Export permission.

To enable this permission, have an administrator:

1. click bring up the Glip Administration console in the web app
2. add the desired API user as an Administrator
3. add the permission by navigating to the "Compliance Exports" section and adding the user under "Who can request and download exports"

Read more in this article which also includes screen shots:

https://medium.com/ringcentral-developers/glip-compliance-exports-api-for-ediscovery-gdpr-and-analytics-d140783527f5

To get a list of Glip organization members, use the Directory Entries API to search and list company contacts. The user id returned in the Directory Entries API is the same as used for the Edit Group Members API.

Search or list company contacts using the following APIs:

• Search Company Directory Entries API
  • https://developer.ringcentral.com/api-reference#Company-Contacts-searchDirectoryEntries
• Get Company Directory Entries API
  • https://developer.ringcentral.com/api-reference#Company-Contacts-listDirectoryEntries

Use the returned user objects' id property with the Edit Group Members API in the addedPersonIds and removedPersonIds properties.

• Edit Group Members API
  • https://developer.ringcentral.com/api-reference#Chats-assignGlipGroupMembers

chats is a new endpoint to cover both Groups and Teams, however PATCH and DELETE have not been implemented on it yet.

Update Team

To update a team, use the old teams endpoint. The teamId below are the same as the chatId provided in the id property returned by the "Get Chat List" API.

Only the following body parameters are supported. Use the one(s) you wish to update.

Users are identified by the Call Log extensionId and the Glip personId which have the same value when the user is a company user.

• In the RingCentral Call Log API, each user is identified by an extensionId.
  • In the Company Call Log API (/restapi/v1.0/account/{accountId}/call-log), you will receive call logs for all users and, to identify calls for each user, you need to query the detailed view by adding the view=Detailed query string parameter and then find the extensionId in the call legs array since multiple users can be present in a call. Each leg will have an extension property with a extensionId and HATEOAS uri property to retrieve information for the user.
  • In the User Call Log API (/restapi/v1.0/account/{accountId}/extension/{extensionId}/call-log), the extensionId is explicitly stated in the URL path.
• In the Glip API, each user is identified by a personId. The personId appears as the creatorId and in other places in the Glip API.
  • When the Glip user is also a RingCentral user, the Glip personId value is the same as the extensionId, e.g. 12345678
  • When the Glip user is a guest and not present in the RingCentral account, the Glip personId value is prefixed by glip-, e.g. glip-12345678

Here's an example of a detailed Company Call Log entry:

Glip recently launched the file upload API which can be used to attach images. You could also try it out using our API Explorer.

Here are answers for the topics you mentioned:

(1) Changing the App after Graduation

The primary thing that cannot be changed is app permissions. This is necessary because app graduation is based on properly exercising selected APIs and when new APIs are added, the app needs to be tested again. Other things can be changed. This is for both public and private apps.

(2) Graduation Process: Public v. Private Apps

Private apps for your company can be automatically graduated by our automated graduation process. Public apps are reviewed by our team to ensure they are behaving properly before being graduated. You can, and we recommend, testing your app in production after graduation from sandbox, but typically our developers are fixing bugs, not adding permissions for new functionality at that point. For public apps, we also recommend you test with some customers before broadly releasing a public app.

Hope this helps. Let us know if you have any other questions.