Curl create ticket, missing signature

Anagastes · July 24, 2019, 7:20am

Used Zammad version: 3.1.x
Used Zammad installation source: Debian-Sourcelist (by Zammad)
Operating system: Debian 9
Browser + version: Chromium 75.0.3770.100, Firefox 68.0.1

Expected behavior:

That an automatic e-mail WITH signature is sent via the CURL command.

Actual behavior:

The e-mail is sent WITHOUT a signature.
Only logged in to Zammad, the signature of the group is automatically added to the user as soon as he creates an e-mail and selects the greetings.

Steps to reproduce the behavior:

Use this CURL-Command.

curl -s --cacert /etc/ssl/certs/cacert.pem
-H “Authorization: Token token=XXX”
-H “Content-Type: application/json”
-X POST -d ‘{“title”: “XXX”, “group”:“First-Level::Second-Level”,“state_id”: 1,“customer”:"’$customer_mail’",“article”:{“content_type”:“text/html”,“origin”:“XXX”,“to”:"’$customer_mail’",“subject”: “XXX”,“body”: "XXX ‘$lname’,“type”: “email”,“internal”: false},“note”:“vServer Install”}’ \https://XXX/api/v1/tickets

Anagastes · August 8, 2019, 6:59pm

No Idea? I need your Help!

MrGeneration · September 9, 2019, 5:28pm

As far as I understand the source code, Zammads WebApp actually is in charge for adding the signature.
Meaning: Zammads API already gets the content with Signature which is why it doesn’t need to add it later on.

I personally would see issues in changing that.

@anon29869905 might correct me here though.

anon29869905 · September 9, 2019, 5:41pm

@MrGeneration is right. The Signature is added by the frontend WebApp and gives the user the freedom to remove or change it at any point. You could fetch the signatures via the signature API endpoint and add it to your text in your calling script.

Anagastes · September 9, 2019, 5:55pm

Great. We missed that part of the API. Where exactly is it documented?

anon29869905 · September 9, 2019, 6:50pm

Our API documentation is not that advanced yet. But it should be pretty straight forward when looking at the code:

github.com

zammad/zammad/blob/develop/config/routes/signature.rb#L5


      
          # Copyright (C) 2012-2024 Zammad Foundation, https://zammad-foundation.org/
          
          Zammad::Application.routes.draw do
            api_path = Rails.configuration.api_path
          
            # signatures
            match api_path + '/signatures',             to: 'signatures#index',   via: :get
            match api_path + '/signatures/:id',         to: 'signatures#show',    via: :get
            match api_path + '/signatures',             to: 'signatures#create',  via: :post
            match api_path + '/signatures/:id',         to: 'signatures#update',  via: :put
            match api_path + '/signatures/:id',         to: 'signatures#destroy', via: :delete
          
          end

github.com

zammad/zammad/blob/develop/app/controllers/signatures_controller.rb#L11


      
          # Copyright (C) 2012-2024 Zammad Foundation, https://zammad-foundation.org/
          
          class SignaturesController < ApplicationController
            prepend_before_action :authenticate_and_authorize!
          
          =begin
          
          Format:
          JSON
          
          Example:
          {
            "id":1,
            "name":"some signature name",
            "body":"some signature body",
            "note":"some note",
            "updated_at":"2012-09-14T17:51:53Z",
            "created_at":"2012-09-14T17:51:53Z",
            "updated_by_id":2,
            "created_by_id":2,
          }

Hope that helps

system · January 7, 2020, 6:50pm

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.