#quro_api

1 messages ¡ Page 1 of 1 (latest)

civic cairnBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1470279018720006216

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

merry dock
#

Sorry, I don't understand your question. What do you mean the deleted object are shared?

naive sequoia
#

types such as

 import Foundation

// ==========================================
// Shared Types (cross-domain)
// ==========================================

/// Information about an error that occurred
/// Used in all V2 API error responses across core, billing, and other namespaces
/// https://docs.stripe.com/api/v2/core/errors
/// https://docs.stripe.com/api/v2/billing/errors
public struct V2ErrorDetails: Sendable, Codable {
    /// Short code to identify the error, should not be handled programmatically
    public var code: String
    
    /// A URL to more information about the error reported
    public var docUrl: String?
    
    /// A human-readable message providing more details about the error
    public var message: String
    
    /// The type of error returned
    public var type: String?
    
    /// A user-friendly message that can be shown to end-users
    public var userMessage: String?
    
    enum CodingKeys: String, CodingKey {
        case code
        case docUrl = "doc_url"
        case message
        case type
        case userMessage = "user_message"
    }
}

/// Stripe error response
/// Used in all V2 API error responses across core, billing, and other namespaces
/// https://docs.stripe.com/api/v2/core/errors
/// https://docs.stripe.com/api/v2/billing/errors
public struct V2Error: Sendable, Codable {
    /// Information about the error that occurred
    public var error: V2ErrorDetails
}

/// Represents a deleted object response
/// Used in V2 API delete operations across multiple domains
/// https://docs.stripe.com/api/v2/core/accounts/persons/delete
/// https://docs.stripe.com/api/v2/core/event_destinations/delete
public struct V2DeletedObject: Sendable, Codable {
    /// The ID of the object that's being deleted
    public var id: String
    
    /// String representing the type of the object that has been deleted
    /// Objects of the same type share the same value of the object field
    public var object: String?
}
#

the problem is understanding the movement from v1 to v2 are there more of such "shared" types to expect?

#

i know just as much as you do?

merry dock
#

For deleted object, their API spec are the same as well

#

Specifications for API errors and deleted object are the same across different APIs

naive sequoia
#

there is no entry in the documentation so i had to ask if this is an edge case or not