Skip to content

Integrations and APIs

72 results found

  1. Allow GetUsers / GetAllUsers to filter by ResourceName / Username

    Currently the API for UsersGetAllUsersV1 only allows for obtaining CondecoID for user based on email address. Since a Condeco user's email address is editable via their profile page, it is not a suitable field to be used to map to Condeco ID. Existing we are using SCIM to sync new user accounts from ActiveDirectory to Condeco. It would be better to obtain CondecoID via ResourceName / Condeco Username using this API.

    Hence, can there be a /api/V1/users?resourceName=<user's condeco username>, so we can retrieve the user's Condeco UserID which is used for all other subsequent API calls like CreateMeeting…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Check-in time parameter

    ‘Allow check-in time’ parameter from screen profile in the API to manage the check-in into meeting space bookings from this parameter. For e.g. if we provide value of this flag as 10 mins, user should be able to start the meeting 10 mins before the actual start time of the booking. The API endpoint which is being used for the check-in is ‘BookingsUpdateMeetingV1’.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. API that will retrieve all the booking created for specific data time range

    Currently there are no endpoint to fetch all booking created in past “X” time period.

    Currently the process would be
    1) Get all desks
    2) Get booking for each of the desk

    Above process would be very time consuming as we may have to traverse thousands of desks.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. The Reduced Capacity Checkbox shouldn't impact the previous setup styles and capacity when posting via Spaces API

    1. Imagine there is a meeting room which has ‘Reduced Capacity’ checked as a Seating Style in the Resource Admin page and as a result of this, other/previous seating styles and capacity with setup and clean down times are greyed out
    2. When the Admin posts a new default room setup style and default capacity from Spaces Master Source application via Spaces API to Condeco, the previous setup styles and capacity with setup and clean down times (if any) will be completely erased and this results in a bad Admin experience

    Suggestion : It would be good if the previous setup styles…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Prevent on-line changes to hierarchy data that is mastered in a different system.

    Our master system for space data is Planon. Changes to the space data are made in this system and posted to Condeco. Unfortunately it is still possible to create space information in Condeco without it being created in Planon and this has resulted in duplicate data (see ENSD-52156 : DeskAzureProd || API Creating Duplicate groups). This results in a very poor user experience because the users can make duplicate desk or room bookings.

    It is requested that Condeco consider:
    • Preventing hierarchy information from being created in Condeco if it is mastered elsewhere OR
    • Warning the user creating or…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. API access to self certification status

    API access to self-certification status would allow us to disable badges and control access if screening is not passed

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepted  ·  0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. More structured field in Getbookings

    Replace th eunique name attribute by two separates attributes: firstname and lastname and check if the mail is still known as the mail of an existaing user of Condeco to avoid the external / internal attribute which relies on mail domain management, that is not efficient in certain context.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. To have Visiting Location and Expected departure date & time in the result of Get Visitor

    In the result of Get Visitor, not all fields are available. Please allow the following data extraction:

    1. Visiting Location (no way to get this for visitor without room booking)

    2. Expected departure date & time

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Token Provider API - Automation

    Please provide the swagger document for the token generation API. We would like to automate the deskbooking API but we are having issues because the token needs to be manually generated

    https://cabs.condecosoftware.com/TokenProviderApi/Token

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Un-mapping a selection of Exchange Rooms at once

    As a Condeco Global Admin - I would like to un-map a selection of Exchange rooms in Condeco. This however seems not possible. All I can do is to click on the "Unmap" button line-by-line.

    When mapping rooms I can highlight more entries at once and click on 'Map selected' button. Something like that is needed for un-mapping rooms.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Additional API for catering management approval

    We need an API for catering rejection of certain orders based on room booking details.

    For example, Catering will be allowed only for room bookings of 4 hours and more, in case the booking was shorter and catering was ordered we can fetch the same by API and reject the catering order separately. The requestor shall get an email notification about the decline of his catering request.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Location API Endpoint - Group Membership

    The current API endpoint available to update a location gives you an option to map all groups that belong to the location using the groups external ID’s. If you do not do this the existing mapped groups are removed.

    This causes an issue as some IWMS systems do not manage all the types of groups that Condeco can manage for example Delivery Point groups, so these groups will need to be added and maintained directly in Condeco. As such they will have no external ID and would not be part of any presync.

    For customers that require regular location updates…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Condeco logs available to the customer SIEM tools (ie Splunk via API?)

    Condeco Cloud collects various logs in relation to interactions the platform has undertaken with other systems and users. For example, who undertook what actions in the tool, who signed in and when, synchronisation to Exchange mailboxes, who requested meetings, who was invited, dates and times, SSO integrations and Office365 integrations, creation/deletion/configuration changes of meeting rooms, desks, user accounts etc.

    Most of these logs are not accessible to the end customers Security Information and Event Management (SIEM) toolsets (i.e. Splunk), and are stored alongside other Condeco customers log data. Because of this it is problematic for Condeco to extract data in…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Retry or Queuing logic to handle events when the notification URL is unavailable

    There are times where the application hosting the notificationURL for a listener event goes down. Today the event logic fires a message to the notificationURL and does not check that the system received the message. To avoid missing events, it would be great if there was a failsafe mechanism that takes advantage of retrying and/or queuing the events in the event that the notificationURL does not respond to events sent to it.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Additional Security on Listener Event Messages

    The ability to specify a token value to be placed in an authorization header on event messages being sent to the notification URL will enhance the security of the receiving application.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. To allow updating Visiting Location & Requestor through Visitor API

    Currently not all fields are available for update. Please allow updating Visiting Location & Requestor through Visitor API

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Need to have a field to specify requestor when creating visitor using Visitor API

    Currently there is no way to specify requestor when creating visitor using the API.
    After visitor is being created, a random user is assigned as the requestor, which does not make sense.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. API endpoints for data analytics

    Current API endpoints are not useful for data analytics purposes. For example /api/v1/deskBookings requires either deskId or userId

    So to get all desk bookings per day in order to analyse who is booking desks where, you have to write a process to get all deskids and then loop through them one by one, appending the results.

    It would be better to have endpoint which provides all desk bookings, with optional parameters as filters.

    This feedback would apply to pretty much every GET endpoint in the API

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. This is a request to increase the number of rooms returned by Bookings_RoomAvailability_v1.

    This is a request to increase the number of rooms returned by BookingsRoomAvailabilityv1. Currently a maximum of 20 rooms and while I realise is for performance reasons, just a few more would cover the number of rooms we have on most but not all of our floors.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Condeco to segregate Delivery Point Groups from the other Groups in interface API

    At present, there is a need to presync delivery groups even though the delivery groups don’t come from Planon. With this request, the APIs will not touch delivery groups when they make any edits in the room hierarchy thus eliminating the need for presyncing delivery groups.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Integrations and APIs

Categories

Feedback and Knowledge Base