- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 8.9
- Kibana concepts
- Quick start
- Set up
- Install Kibana
- Configure Kibana
- Alerting and action settings
- APM settings
- Banners settings
- Cases settings
- Enterprise Search settings
- Fleet settings
- i18n settings
- Logging settings
- Logs settings
- Metrics settings
- Monitoring settings
- Reporting settings
- Search sessions settings
- Secure settings
- Security settings
- Spaces settings
- Task Manager settings
- Telemetry settings
- URL drilldown settings
- Start and stop Kibana
- Access Kibana
- Securing access to Kibana
- Add data
- Upgrade Kibana
- Configure security
- Configure reporting
- Configure logging
- Configure monitoring
- Command line tools
- Production considerations
- Discover
- Dashboard and visualizations
- Canvas
- Maps
- Build a map to compare metrics by country or region
- Track, visualize, and alert on assets in real time
- Map custom regions with reverse geocoding
- Heat map layer
- Tile layer
- Vector layer
- Plot big data
- Search geographic data
- Configure map settings
- Connect to Elastic Maps Service
- Import geospatial data
- Troubleshoot
- Reporting and sharing
- Machine learning
- Graph
- Alerting
- Observability
- APM
- Set up
- Get started
- How-to guides
- Configure APM agents with central config
- Control access to APM data
- Create an alert
- Create custom links
- Filter data
- Find transaction latency and failure correlations
- Identify deployment details for APM agents
- Integrate with machine learning
- Observe Lambda functions
- Query your data
- Storage Explorer
- Track deployments with annotations
- Users and privileges
- Settings
- REST API
- Troubleshooting
- Security
- Dev Tools
- Fleet
- Osquery
- Stack Monitoring
- Stack Management
- REST API
- Get features API
- Kibana spaces APIs
- Kibana role management APIs
- User session management APIs
- Saved objects APIs
- Data views API
- Index patterns APIs
- Alerting APIs
- Action and connector APIs
- Cases APIs
- Add comment
- Create case
- Delete cases
- Delete comments
- Find case activity
- Find cases
- Find connectors
- Get alerts
- Get case activity
- Get case
- Get case status
- Get cases by alert
- Get comments
- Get configuration
- Get reporters
- Get tags
- Push case
- Set configuration
- Update cases
- Update comment
- Update configuration
- Import and export dashboard APIs
- Logstash configuration management APIs
- Machine learning APIs
- Osquery manager API
- Short URLs APIs
- Get Task Manager health
- Upgrade assistant APIs
- Kibana plugins
- Troubleshooting
- Accessibility
- Release notes
- Kibana 8.9.2
- Kibana 8.9.1
- Kibana 8.9.0
- Kibana 8.8.2
- Kibana 8.8.1
- Kibana 8.8.0
- Kibana 8.7.1
- Kibana 8.7.0
- Kibana 8.6.1
- Kibana 8.6.0
- Kibana 8.5.2
- Kibana 8.5.1
- Kibana 8.5.0
- Kibana 8.4.3
- Kibana 8.4.2
- Kibana 8.4.1
- Kibana 8.4.0
- Kibana 8.3.3
- Kibana 8.3.2
- Kibana 8.3.1
- Kibana 8.3.0
- Kibana 8.2.3
- Kibana 8.2.2
- Kibana 8.2.1
- Kibana 8.2.0
- Kibana 8.1.3
- Kibana 8.1.2
- Kibana 8.1.1
- Kibana 8.1.0
- Kibana 8.0.0
- Kibana 8.0.0-rc2
- Kibana 8.0.0-rc1
- Kibana 8.0.0-beta1
- Kibana 8.0.0-alpha2
- Kibana 8.0.0-alpha1
- Developer guide
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Push case API
editPush case API
editPushes a case to an external service.
For the most up-to-date API details, refer to the open API specification.
Request
editPOST <kibana host>:<port>/api/cases/<case_id>/connector/<connector_id>/_push
POST <kibana host>:<port>/s/<space_id>/api/cases/<case_id>/connector/<connector_id>/_push
Prerequisites
editYou must have all
privileges for the Actions and Connectors feature in the
Management section of the
Kibana feature privileges. You must also have all
privileges for the Cases feature in the Management, Observability, or
Security section of the Kibana feature privileges, depending on the
owner
of the case you’re pushing.
Path parameters
edit-
<case_id>
- (Required, string) The identifier for the case. To retrieve case IDs, use Find cases.
-
<connector_id>
- (Required, string) The identifier for the connector. To retrieve connector IDs, use Find connectors.
- <space_id>
- (Optional, string) An identifier for the space. If it is not specified, the default space is used.
Response codes
edit-
200
- Indicates a successful call.
Examples
editPush the case to an external service:
POST api/cases/b917f300-0ed9-11ed-bd18-65557fe66949/connector/09f8c0b0-0eda-11ed-bd18-65557fe66949/_push {}
The API returns a JSON object representing the pushed case. For example:
{ "id": "b917f300-0ed9-11ed-bd18-65557fe66949", "version": "WzE3NjgsM10=", "comments": [], "totalComment": 0, "totalAlerts": 0, "description": "A case description.", "title": "Case title 1", "tags": [ "tag 1" ], "settings": { "syncAlerts": true }, "owner": "cases", "duration": null, "severity": "low", "closed_at": null, "closed_by": null, "created_at": "2022-07-29T00:59:39.444Z", "created_by": { "username": "elastic", "email": null, "full_name": null }, "status": "open", "updated_at": "2022-07-29T01:20:58.436Z", "updated_by": { "username": "elastic", "full_name": null, "email": null }, "connector": { "id": "09f8c0b0-0eda-11ed-bd18-65557fe66949", "name": "My connector", "type": ".jira", "fields": { "issueType": "10006", "parent": null, "priority": "Low" } }, "external_service": { "pushed_at": "2022-07-29T01:20:58.436Z", "pushed_by": { "username": "elastic", "full_name": null, "email": null }, "connector_name": "My connector", "external_id": "71926", "external_title": "ES-554", "external_url": "https://cases.jira.com", "connector_id": "09f8c0b0-0eda-11ed-bd18-65557fe66949" } }
Was this helpful?
Thank you for your feedback.